Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 69 15 Dec 2024, 07:36

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:22.443
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 9.346
And I wait until Tor is ready 1.628
When I disconnect the network through GNOME 2.622
And I connect the network through GNOME 2.802
Then the Tor Connection Assistant autostarts 2.440
And the Tor Connection Assistant connects to Tor 3.398
And I wait until Tor is ready 5:0.203
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:704:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:702:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:655:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 5.152 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:01)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.033
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:22.552
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.351
And I prepare Tails for memory erasure tests 0.454
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 38.513
And I fill the USB drive with a known pattern 1.481
And I read the content of the test FS 0.068
And patterns cover at least 99% of the test FS size in the guest's memory 2.743 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.669
And I wait for Tails to finish wiping the memory 1:30.270
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:326 10.615 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:58:00)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/01:58:00_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/01:58:00_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/01:58:00_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product
1:39.016
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.206
And I start the computer from DVD with network unplugged 37.850
When Tails detects disk read failures on the boot device with a target error 0.887
Then I see a disk failure message on the splash screen 1:0.072
cannot 
cannot find PlymouthDiskFailureMessage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/hardware.rb:62:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:16:in `Then I see a disk failure message on the splash screen'
features/hardware_failure.feature:11:in `Then I see a disk failure message on the splash screen'
After features/support/hooks.rb:326 4.780 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#3)' (at time 02:15:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/02:15:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/02:15:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/02:15:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/02:15:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.journal
After features/support/hooks.rb:100 0.009
Feature: Tails persistence
Tags: @product
22:38.340
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 12.980
Then Tails is running from USB drive "__internal" 0.369
When I create a file in the Persistent directory 0.133
And I create a persistent partition with the default settings 18.217
Then the file I created was copied to the Persistent Storage 0.440
When I shutdown Tails and wait for the computer to power off 12.522
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:53.676
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/persistence.feature:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:326 10.827 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 03:26:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/03:26:50_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/03:26:50_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/69/artifact/build-artifacts/03:26:50_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.009