Project Number Date
test_Tails_ISO_test-suite-options 13 29 Jun 2025, 20:59

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product
1:51.328
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.078
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./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:459: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:459: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_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.776 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:55:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
3:35.688
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Steps
Given a computer 0.332
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:27.034
Then all tps features from the old Tails version are active 3.715
And Tails is running from USB drive "to_upgrade" 0.674
And the boot device has safe access rights 3.872
And the expected persistent files created with the old Tails version are present in the filesystem 0.059
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:21:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1097:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1096:in `each'
./features/step_definitions/usb.rb:1096:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 6.420 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:02:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Feature: Backing up the persistent storage
Tags: @product
1:38.585
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.481
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 16.113
And I clone USB drive "__internal" to a temporary USB drive "backup" 3.991
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.804
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.082
When I start Tails' custom backup tool 6.144
Then the backup tool displays "Plug in your backup Tails USB stick" 0.255
When I plug USB drive "backup" 2.571
And I give the Persistent Storage on drive "backup" its own UUID 0.186
And I click "Retry" in the backup tool 1.251
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.262
When I click "Back Up" in the backup tool 1.298
And I enter my persistent storage passphrase into the polkit prompt 5.139
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.002
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "zenity" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/backup.rb:7:in `new'
./features/step_definitions/backup.rb:7:in `block (2 levels) in <top (required)>'
./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/backup.rb:6: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/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 10.121 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:24:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:24:00_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:24:00_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:24:00_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:24:00_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 1.351
Feature: Tails persistence
Tags: @product
15.979
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 10.541
And I log in to a new session without activating the Persistent Storage 5.438
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:519:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 5.222 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 04:32:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/04:32:31_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/04:32:31_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/04:32:31_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/04:32:31_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
1:47.939
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.844
And I capture all network traffic 0.052
When I successfully start the Unsafe Browser 22.515
And I open the Tails homepage in the Unsafe Browser 10.514
And the Tails homepage loads in the Unsafe Browser 1:0.012
cannot 
cannot find TailsHomepage.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:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:20:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.589 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:23:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:23:41_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:23:41_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:23:41_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:23:41_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.048
Feature: Browsing the web using the Unsafe Browser
Tags: @product
1:48.744
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.241
When I successfully start the Unsafe Browser 23.917
When I open the Tails homepage in the Unsafe Browser 11.384
Then the Tails homepage loads in the Unsafe Browser 1:0.201
cannot 
cannot find TailsHomepage.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:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:38:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 7.212 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 05:59:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:59:42_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:59:42_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:59:42_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/05:59:42_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
39.266
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 29.059
And I unlock and mount this VeraCrypt file container with GNOME Disks 10.206
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.786 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 06:11:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/06:11:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/06:11:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/06:11:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/06:11:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.014