Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 1 20 Aug 2026, 15:05

Failures Overview

The following summary displays scenarios that failed.

Feature: Root access control enforcement
Tags: @product
52.039
Scenario I cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Steps
Given I have started Tails from DVD without network and logged in 28.611
And running a command as root with pkexec requires PolicyKit administrator privileges 0.063
Then I cannot run a command as root with sudo and the standard passwords 0.234
And I cannot run a command as root with pkexec and the standard passwords 23.129
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/common_steps.rb:1026:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/root_access_control.rb:57:in `/^I cannot run a command as root with pkexec and the standard passwords$/'
features/root_access_control.feature:16:in `And I cannot run a command as root with pkexec and the standard passwords'
Then I cannot login as root using su with the standard passwords 0.000
After features/support/hooks.rb:339 4.982 
SCENARIO FAILED: 'I cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen' (at time 00:13:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/00:13:33_I_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/00:13:33_I_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/00:13:33_I_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/00:13:33_I_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal
After features/support/hooks.rb:108 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
21.877
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.745
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.265
When the network is plugged 0.032
And Tor is ready 15.290
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
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/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:713:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:667:in `/^Tor is ready$/'
features/usb_upgrade.feature:89:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:339 5.292 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:16:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:16:13_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:16:13_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:16:13_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:16:13_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
47.229
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD without network and logged in 3.758
And I prepare Tails for memory erasure tests 0.346
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 43.124
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/common_steps.rb:847:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1610:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/emergency_shutdown.feature:39:in `And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
And I fill the USB drive with a known pattern 0.000
And I read the content of the test FS 0.000
And patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:339 5.178 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:19:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:19:04_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:19:04_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:19:04_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:19:04_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:108 0.002
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:51.533
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.945
And I prepare Tails for memory erasure tests 0.521
And I fill a 128 MiB file with a known pattern on the persistent filesystem 11.595
And patterns cover at least 100 MiB in the guest's memory 2.951 
Pattern coverage: 128.000% (128 MiB out of 100 MiB reference memory)
When I eject the boot medium 0.387
And I wait for Tails to finish wiping the memory 1:30.131
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:53:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:339 5.204 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 01:21:01)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:21:01_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:21:01_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:21:01_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:108 0.000
Feature: Tails persistence
Tags: @product
56.178
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 56.178
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
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/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:713:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:667:in `/^Tor is ready$/'
./features/step_definitions/snapshots.rb:208:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:205:in `each'
./features/step_definitions/snapshots.rb:205:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:227:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/persistence.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update the APT lists using apt 0.000
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:339 4.859 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 02:19:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/02:19:00_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/02:19:00_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/02:19:00_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/02:19:00_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
33.700
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Before features/support/hooks.rb:527 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 6.994
When I start the Tor Browser 26.706
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:517:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:507:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:75:in `When I start the Tor Browser'
When I open the address "https://example.com/" in the Tor Browser 0.000
Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page 0.000
And the Tor Browser has 2 tabs open 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser loads about:tor 0.000
And the Tor Browser has 1 tab open 0.000
After features/support/hooks.rb:535 0.043
After features/support/hooks.rb:339 5.786 
SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 03:02:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:02:50_The_Tor_Browser_s__New_identity__feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:02:50_The_Tor_Browser_s__New_identity__feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:02:50_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:02:50_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:6.265
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and logged in 3.723
Then the live user's Downloads directory exists 0.043
And there is a GNOME bookmark for the Downloads directory 1:2.498
try_for() 
try_for() timeout expired
Last ignored exception was: Test::Unit::AssertionFailedError: <Dogtail::Failure> exception was expected but none was thrown.
./features/step_definitions/common_steps.rb:1300:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187: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:1298:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:1341: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:1298:in `/^I close the "([^"]+)" window via AltF4$/'
./features/step_definitions/common_steps.rb:1341:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:124:in `And there is a GNOME bookmark for the Downloads directory'
features/torified_browsing.feature:118:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Downloads GNOME bookmark 0.000
After features/support/hooks.rb:339 5.345 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 03:06:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:06:54_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:06:54_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:06:54_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:06:54_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal
After features/support/hooks.rb:108 0.000
Feature: I can report a bug with WhisperBack
Tags: @product
22.205
Scenario WhisperBack has access to debugging information
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and logged in 3.427
When I start "WhisperBack" via GNOME Activities Overview 8.527
Then WhisperBack has debugging information 10.250
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'whisperback' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/whisperback.rb:2:in `new'
./features/step_definitions/whisperback.rb:2:in `whisperback'
./features/step_definitions/whisperback.rb:10:in `/^WhisperBack has debugging information$/'
features/whisperback.feature:19:in `Then WhisperBack has debugging information'
After features/support/hooks.rb:339 5.261 
SCENARIO FAILED: 'WhisperBack has access to debugging information' (at time 03:27:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:27:06_WhisperBack_has_access_to_debugging_information.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:27:06_WhisperBack_has_access_to_debugging_information.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:27:06_WhisperBack_has_access_to_debugging_information.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/03:27:06_WhisperBack_has_access_to_debugging_information.journal
After features/support/hooks.rb:108 0.000