Project Number Date
test_Tails_ISO_20522-ocr-more 8 18 Dec 2024, 05:18

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:12.036
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.331
And I power off the computer 0.332
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.345
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.542 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 00:55:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/00:55:54_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/00:55:54_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/00:55:54_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.068
Feature: Additional software
Tags: @product @check_tor_leaks @slow
2:30.139
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:269 0.004
Before features/support/hooks.rb:507 0.004
Steps
Given a computer 0.180
And I start Tails from USB drive "__internal" and I login with an administration password 2:29.958
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:300: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/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update APT using apt 0.000
When I install "makepp" using apt 0.000
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.048
After features/support/hooks.rb:326 14.156 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:11:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/01:11:42_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/01:11:42_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/01:11:42_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/01:11:42_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Hardware failures
Tags: @product @doc
20.001
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.187
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.161
When Tails detects disk read failures on the SquashFS 0.647
Then I see a disk failure message 10.004
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.385 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:11:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:11:27_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/8/artifact/build-artifacts/02:11:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:11:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:11:27_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.371
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.181
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.325
When Tails detects disk read failures on the boot device 0.862
Then I see a disk failure message 10.002
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.354 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:11:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:11:52_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/8/artifact/build-artifacts/02:11:52_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:11:52_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:11:52_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.946
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.003
Steps
Given a computer 0.199
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.802
When Tails detects disk read failures on the boot device with a target error 0.942
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.336 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:12:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:12:19_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/8/artifact/build-artifacts/02:12:19_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:12:19_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/02:12:19_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:39.198
Scenario The persistent Tor Browser directory is usable
Before features/support/hooks.rb:269 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.650
And the network is plugged 0.082
And I successfully configure Tor 21.142
And available upgrades have been checked 1.113
And all notifications have disappeared 4.214
Then the persistent Tor Browser directory exists 0.079
And there is a GNOME bookmark for the persistent Tor Browser directory 1.710
When I start the Tor Browser 22.135
And I open the address "https://tails.net/about" in the Tor Browser 16.021
And "Tails - How Tails works" has loaded in the Tor Browser 1.352
Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark 19.694
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.505 
SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 04:11:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/04:11:13_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/8/artifact/build-artifacts/04:11:13_The_persistent_Tor_Browser_directory_is_usable.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/04:11:13_The_persistent_Tor_Browser_directory_is_usable.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/8/artifact/build-artifacts/04:11:13_The_persistent_Tor_Browser_directory_is_usable.journal
After features/support/hooks.rb:100 0.000