Project Number Date
test_Tails_ISO_devel 3872 17 Jun 2025, 22:53

Failures Overview

The following summary displays scenarios that failed.

Feature: Backing up the persistent storage
Tags: @product
1:39.302
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.018
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.713
# 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 13.691
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.956
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.215
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.018
When I start Tails' custom backup tool 7.281
Then the backup tool displays "Plug in your backup Tails USB stick" 1.330
When I plug USB drive "backup" 4.276
And I give the Persistent Storage on drive "backup" its own UUID 0.148
And I click "Retry" in the backup tool 1.233
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.277
When I click "Back Up" in the backup tool 1.160
And I enter my persistent storage passphrase into the polkit prompt 3.991
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.006
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/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 8.323 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:56:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/02:56:17_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_devel/3872/artifact/build-artifacts/02:56:17_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/02:56:17_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/02:56:17_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.237
Feature: Hardware failures
Tags: @product @broken_welcome_screen
1:53.062
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.394
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 2.248
Then the computer boots Tails 50.406
And I see a disk failure message on the splash screen 1:0.012
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:43:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:17:in `And I see a disk failure message on the splash screen'
features/hardware_failure.feature:13:in `And I see a disk failure message on the splash screen'
After features/support/hooks.rb:330 8.189 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 03:13:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:13:30_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:13:30_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:13:30_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:13:30_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal
After features/support/hooks.rb:100 0.059
Feature: Hardware failures
Tags: @product
4:48.881
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
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.615
And I corrupt the boot device's GPT backup partition table 0.369
And I power off the computer 0.543
When I start the computer 1.143
Then the computer boots Tails 1:25.106
When I log in to a new session 3:5.103
cannot 
cannot find GnomeApplicationsMenu.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/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522: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/hardware_failure.feature:46:in `When I log in to a new session'
features/hardware_failure.feature:39:in `When I log in to a new session'
And all notifications have disappeared 0.000
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.766 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:25:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:25:54_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:25:54_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:25:54_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:25:54_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.024
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:25.994
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.778
When I log in to a new session in Chinese (zh_CN) 42.475
Then the keyboard layout is set to "cn" 0.276
When the network is plugged 0.096
And Tor is ready 26.664
Then I successfully start the Unsafe Browser 25.945
And I kill the Unsafe Browser 6.933
When I enable the screen keyboard 0.144
Then the screen keyboard works in Tor Browser 31.680
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:45:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.569 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:51:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:51:40_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:51:40_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:51:40_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/03:51:40_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:34.927
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 14.588
When I log in to a new session in Russian (ru) 44.057
Then the keyboard layout is set to "ru" 0.186
When the network is plugged 0.102
And Tor is ready 24.527
Then I successfully start the Unsafe Browser 31.761
And I kill the Unsafe Browser 6.844
When I enable the screen keyboard 0.126
Then the screen keyboard works in Tor Browser 32.733
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:55:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "ru" 0.000
After features/support/hooks.rb:330 8.118 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:16:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:16:21_Tails_is_localized_for_every_tier-1_language,_Examples___9_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:16:21_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:16:21_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:16:21_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:15.372
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 25.142
When I log in to a new session in Turkish (tr) 54.550
Then the keyboard layout is set to "tr" 0.597
When the network is plugged 0.100
And Tor is ready 36.285
Then I successfully start the Unsafe Browser 37.218
And I kill the Unsafe Browser 6.744
When I enable the screen keyboard 0.197
Then the screen keyboard works in Tor Browser 34.535
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:57:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 12.157 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 04:24:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:24:42_Tails_is_localized_for_every_tier-1_language,_Examples___11_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:24:42_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:24:42_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:24:42_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
1:46.625
Scenario MAC address spoofing is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 43.947
And I capture all network traffic 0.532
When I log in to a new session 45.363
And the network is plugged 4.633
And Tor is ready 12.148
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/mac_spoofing.feature:27:in `And Tor is ready'
Then 1 network interface is enabled 0.000
And the 1st network device has a spoofed MAC address configured 0.000
When I hotplug a network device and wait for it to be initialized 0.000
Then 2 network interfaces are enabled 0.000
And the 2nd network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 9.160 
SCENARIO FAILED: 'MAC address spoofing is successful' (at time 04:28:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:28:18_MAC_address_spoofing_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:28:18_MAC_address_spoofing_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:28:18_MAC_address_spoofing_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:28:18_MAC_address_spoofing_is_successful.journal
After features/support/hooks.rb:100 0.048
Feature: Tails persistence
Tags: @product
1:14.145
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:14.145
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173: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 APT 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:330 5.295 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 04:42:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:42:19_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:42:19_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:42:19_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/04:42:19_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:18.860
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:18.860
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167: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/persistence.feature:73:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And Tor is ready 0.000
And I take note of which tps features are available 0.000
When I write some files expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?
Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 7.373 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 05:02:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:02:01_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:02:01_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:02:01_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:02:01_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
5:45.404
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.621
And the network is plugged 0.081
And Tor is ready 37.045
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.402
And I shutdown Tails and wait for the computer to power off 18.725
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:12.733
And I capture all network traffic 0.079
And the network is plugged 0.570
And Tor is ready 15.144
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/persistence.feature:91:in `And Tor is ready'
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 7.302 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 05:07:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:07:55_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:07:55_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:07:55_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:07:55_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.091
Feature: Tails persistence
Tags: @product
1:27.381
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.130
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:27.381
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:103:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
When I enable persistence 0.000
Then no persistent Greeter options were restored 0.000
When I set all Greeter options to non-default values 0.000
And I log in to a new session in German (de) after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
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:330 5.839 
SCENARIO FAILED: 'Persistent Greeter options' (at time 05:12:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:12:02_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:12:02_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:12:02_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3872/artifact/build-artifacts/05:12:02_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000