Project Number Date
test_Tails_ISO_stable 5153 07 Oct 2024, 18:20

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:15.095
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.012
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.929
And I power off the computer 0.354
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.783
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:240:in `rescue in wait_any'
./features/support/helpers/screen.rb:224: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.560 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 00:58:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/00:58:29_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/00:58:29_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/00:58:29_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.112
Feature: Tails persistence
Tags: @product
21:27.868
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.725
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.110
When I try to enable persistence 0.301
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 35.596
When I repair the filesystem of the Persistent Storage 1.263
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.074
When I log in to a new session 40.679
And all notifications have disappeared 20:0.116
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/persistence.feature:191:in `And all notifications have disappeared'
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage, if the Persistent Storage doesn't unlock" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:326 10.920 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 03:58:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/03:58:50_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/03:58:50_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/03:58:50_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
4:12.627
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.809
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.216
And Tails detects disk read failures on the boot device 1.644
When I try to enable persistence 0.455
Then the Welcome Screen tells me that my hardware is probably failing 6.617
When I log in to a new session 21.456
And all notifications have disappeared 5.007
Then the Tor Browser starts 22.305
And "Tails - Recovering data from the Persistent Storage, if the Persistent Storage doesn't unlock" has loaded in the Tor Browser 3:0.113
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:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:215:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/persistence.feature:212:in `And "Tails - Recovering data from the Persistent Storage, if the Persistent Storage doesn't unlock" has loaded in the Tor Browser'
After features/support/hooks.rb:326 5.587 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:03:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/04:03:14_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/04:03:14_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/04:03:14_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5153/artifact/build-artifacts/04:03:14_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000