Project Number Date
test_Tails_ISO_20522-ocr-more 4 14 Dec 2024, 05:23

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:21.095
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 5.926
And I wait until Tor is ready 3.922
When I disconnect the network through GNOME 2.758
And I connect the network through GNOME 2.722
Then the Tor Connection Assistant autostarts 2.272
And the Tor Connection Assistant connects to Tor 3.088
And I wait until Tor is ready 5:0.406
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.105 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:04)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/00:31:04_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/00:31:04_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_20522-ocr-more/4/artifact/build-artifacts/00:31:04_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/00:31:04_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/00:31:04_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/00:31:04_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/00:31:04_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.032
Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:12.738
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.093
And I power off the computer 0.347
And the computer is set to boot in UEFI mode 0.027
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.270
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuGRUB_Bullseye.png", "TailsBootMenuGRUB_Bookworm.png"] on the screen
./features/support/helpers/screen.rb:246:in `rescue in wait_any'
./features/support/helpers/screen.rb:230:in `wait_any'
./features/step_definitions/common_steps.rb:407:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/usb_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:326 10.571 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:00:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/01:00:52_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/01:00:52_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/01:00:52_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.066
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:18.151
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.193
And I prepare Tails for memory erasure tests 0.439
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 34.604
And I fill the USB drive with a known pattern 1.511
And I read the content of the test FS 0.070
And patterns cover at least 99% of the test FS size in the guest's memory 2.831 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.393
And I wait for Tails to finish wiping the memory 1:30.108
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.828 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:56:14)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/01:56:14_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/01:56:14_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/01:56:14_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 @doc
21.270
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.176
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.644
When Tails detects disk read failures on the SquashFS 0.447
Then I see a disk failure message 10.001
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:27:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.380 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:13:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.245
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.189
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.424
When Tails detects disk read failures on the boot device 0.629
Then I see a disk failure message 10.001
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:28:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.322 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:13:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:13:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
33.980
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.178
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.238
When Tails detects disk read failures on the boot device with a target error 0.562
Then I see a disk failure message 10.001
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.438 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:14:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:14:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:14:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:14:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/02:14:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:46.228
Scenario The persistent Tor Browser directory is usable
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.844
And the network is plugged 0.081
And I successfully configure Tor 22.544
And available upgrades have been checked 0.059
And all notifications have disappeared 4.176
Then the persistent Tor Browser directory exists 0.053
And there is a GNOME bookmark for the persistent Tor Browser directory 1.726
When I start the Tor Browser 22.649
And I open the address "https://tails.net/about" in the Tor Browser 18.747
And "Tails - How Tails works" has loaded in the Tor Browser 1.112
Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark 20.231
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:558:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark'
And I open the address "file:///home/amnesia/Persistent/Tor Browser/index.html" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the persistent Tor Browser directory 0.000
After features/support/hooks.rb:326 6.998 
SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 04:15:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:15:15_The_persistent_Tor_Browser_directory_is_usable.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:15:15_The_persistent_Tor_Browser_directory_is_usable.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:15:15_The_persistent_Tor_Browser_directory_is_usable.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:15:15_The_persistent_Tor_Browser_directory_is_usable.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
31.712
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.082
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 15.629
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/veracrypt.rb:190:in `/^I unlock and mount this VeraCrypt (volume|file container) with Unlock VeraCrypt Volumes$/'
features/veracrypt.feature:32:in `And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:326 6.546 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 04:37:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:37:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:37:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:37:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/4/artifact/build-artifacts/04:37:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000