Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 10 29 Oct 2024, 20:03

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
7:4.442
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:4.442
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.990 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:40:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/10/artifact/build-artifacts/00:40:09_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/10/artifact/build-artifacts/00:40:09_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/10/artifact/build-artifacts/00:40:09_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/10/artifact/build-artifacts/00:40:09_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.012
Feature: Tails persistence
Tags: @product
4:11.799
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 13.560
When I enable persistence 40.643
Then no persistent Greeter options were restored 15.472
When I set all Greeter options to non-default values 29.626
And I log in to a new session in German (de) after having activated the Persistent Storage 54.214
Then all Greeter options are set to non-default values 0.438
When I cold reboot the computer 8.879
And the computer reboots Tails 1:1.335
Given I enable persistence 27.628
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.285 
SCENARIO FAILED: 'Persistent Greeter options' (at time 03:32:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/10/artifact/build-artifacts/03:32:55_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/10/artifact/build-artifacts/03:32:55_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/10/artifact/build-artifacts/03:32:55_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/10/artifact/build-artifacts/03:32:55_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.008
Feature: Tails persistence
Tags: @product
2:9.597
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.951
And I enable persistence but something goes wrong during the LUKS header upgrade 2:0.646
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/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.878 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:50:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/10/artifact/build-artifacts/03:50:22_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/10/artifact/build-artifacts/03:50:22_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/10/artifact/build-artifacts/03:50:22_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/10/artifact/build-artifacts/03:50:22_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:100 0.000