Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 11 30 Oct 2024, 20:16

Failures Overview

The following summary displays scenarios that failed.

6:15.092
Scenario Erasure of read and write disk caches of persistent data on shutdown
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 6:15.092
The
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:326 5.335

SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:40:27)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/00:40:27_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/00:40:27_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/00:40:27_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/00:40:27_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:100 0.013
Tags: @product @uefi
3:15.740
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 13.982
And I power off the computer 0.347
And the computer is set to boot in UEFI mode 0.035
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.374
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.613

SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:05:33)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/01:05:33_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/01:05:33_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/01:05:33_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal

After features/support/hooks.rb:100 0.086
Tags: @product
4:9.916
Scenario Persistent Greeter options
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 16.717
When I enable persistence 36.117
Then no persistent Greeter options were restored 18.091
When I set all Greeter options to non-default values 26.330
And I log in to a new session in German (de) after having activated the Persistent Storage 58.371
Then all Greeter options are set to non-default values 0.746
When I cold reboot the computer 7.950
And the computer reboots Tails 1:1.344
Given I enable persistence 24.246
The
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:111:in `Given I enable persistence'
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:326 5.399

SCENARIO FAILED: 'Persistent Greeter options' (at time 03:31:02)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:31:02_Persistent_Greeter_options.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:31:02_Persistent_Greeter_options.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:31:02_Persistent_Greeter_options.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:31:02_Persistent_Greeter_options.journal

After features/support/hooks.rb:100 0.007
Tags: @product
2:9.261
Scenario LUKS backup header is restored if something goes wrong during upgrade
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 8.565
And I enable persistence but something goes wrong during the LUKS header upgrade 2:0.695
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/usb.rb:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:712:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:326 4.825

SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:46:57)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:46:57_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:46:57_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:46:57_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/11/artifact/build-artifacts/03:46:57_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal

After features/support/hooks.rb:100 0.000