Project Number Date
test_Tails_ISO_21014-htpdateerror 2 14 Jun 2025, 00:20

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
24.650
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 13.658
And I make sure time sync before Tor connects times out 1.147
When the network is plugged 0.081
And I successfully configure Tor 9.762
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/time_syncing.feature:59:in `And I successfully configure Tor'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.076
After features/support/hooks.rb:330 5.387 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:23:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/00:23:35_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/00:23:35_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/00:23:35_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/00:23:35_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.002
Feature: Hardware failures
Tags: @product
4:51.780
Scenario Outline GPT backup corruption with a persistent partition
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 and stopped at Tails Greeter's login screen 11.452
And I corrupt the boot device's GPT backup partition table 0.577
And I power off the computer 0.585
When I start the computer 2.070
Then the computer boots Tails 1:29.698
When I log in to a new session 3:7.396
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 5.442 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:04:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:04:58_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_21014-htpdateerror/2/artifact/build-artifacts/03:04:58_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:04:58_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:04:58_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.013
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:20.227
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.018
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 27.748
When I log in to a new session in Arabic (ar) 56.488
Then the keyboard layout is set to "us" 0.449
When the network is plugged 0.518
And Tor is ready 35.745
Then I successfully start the Unsafe Browser 37.142
And I kill the Unsafe Browser 7.094
When I enable the screen keyboard 0.187
Then the screen keyboard works in Tor Browser 34.853
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:44: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.002 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 03:32:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:32:25_Tails_is_localized_for_every_tier-1_language,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:32:25_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:32:25_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:32:25_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
5:6.955
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.060
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 13.353
When I log in to a new session in Chinese (zh_CN) 58.174
Then the keyboard layout is set to "cn" 0.531
When the network is plugged 0.111
And Tor is ready 34.667
Then I successfully start the Unsafe Browser 40.095
And I kill the Unsafe Browser 6.797
When I enable the screen keyboard 0.329
Then the screen keyboard works in Tor Browser 58.986
And DuckDuckGo is the default search engine 55.546
And I kill the Tor Browser 7.697
And the screen keyboard works in Thunderbird 30.664
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Thunderbird" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1047:in `new'
./features/step_definitions/common_steps.rb:1047:in `block in launch_app'
./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:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `block in <top (required)>'
./features/step_definitions/thunderbird.rb:212: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:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `/^I start Thunderbird$/'
./features/step_definitions/thunderbird.rb:212:in `/^the screen keyboard works in Thunderbird$/'
features/localization.feature:45:in `And the screen keyboard works in Thunderbird'
features/localization.feature:33:in `And the screen keyboard works in Thunderbird'
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 15.489 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:37:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:37:44_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:37:44_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/03:37:44_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
3:13.270
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.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 18.351
When I log in to a new session in Russian (ru) 58.981
Then the keyboard layout is set to "ru" 0.184
When the network is plugged 0.086
And Tor is ready 37.810
Then I successfully start the Unsafe Browser 36.950
And I kill the Unsafe Browser 7.049
When I enable the screen keyboard 0.179
Then the screen keyboard works in Tor Browser 33.676
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 12.666 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:10:04)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:10:04_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:10:04_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:10:04_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
34.148
Scenario MAC address spoofing is disabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 19.463
And I capture all network traffic 0.018
When I disable MAC spoofing in Tails Greeter 14.666
cannot 
cannot find TailsGreeterDisableMACSpoofing.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/mac_spoofing.rb:13:in `/^I disable MAC spoofing in Tails Greeter$/'
features/mac_spoofing.feature:11:in `When I disable MAC spoofing in Tails Greeter'
And I log in to a new session 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then 1 network interface is enabled 0.000
And the 1st network device has its real 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 its real MAC address configured 0.000
And some network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 6.547 
SCENARIO FAILED: 'MAC address spoofing is disabled' (at time 04:20:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:20:42_MAC_address_spoofing_is_disabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:20:42_MAC_address_spoofing_is_disabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:20:42_MAC_address_spoofing_is_disabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:20:42_MAC_address_spoofing_is_disabled.journal
After features/support/hooks.rb:100 0.057
Feature: Spoofing MAC addresses
Tags: @product
3:54.428
Scenario MAC address spoofing is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 42.793
And I capture all network traffic 0.394
When I log in to a new session 3:11.241
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/mac_spoofing.feature:25:in `When I log in to a new session'
And the network is plugged 0.000
And Tor is ready 0.000
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 6.131 
SCENARIO FAILED: 'MAC address spoofing is successful' (at time 04:24:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:24:44_MAC_address_spoofing_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:24:44_MAC_address_spoofing_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:24:44_MAC_address_spoofing_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:24:44_MAC_address_spoofing_is_successful.journal
After features/support/hooks.rb:100 0.051
Feature: Tails persistence
Tags: @product
3:13.875
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 3:13.875
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: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 7.625 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 04:41:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:41:59_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:41:59_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:41:59_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:41:59_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
36.885
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 24.839
When I log in to a new session without activating the Persistent Storage 12.046
<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:14:in `When I log in to a new session without activating the Persistent Storage'
Then Tails is running from USB drive "__internal" 0.000
And persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
After features/support/hooks.rb:330 6.224 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 04:42:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:42:42_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:42:42_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:42:42_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:42:42_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:30.513
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.048
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:30.513
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\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistence.feature:20:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
Then Tails is running from USB drive "__internal" 0.000
When I create a file in the Persistent directory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
When I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 5.508 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 04:44:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:44:19_Creating_a_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:44:19_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:44:19_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:44:19_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:16.084
Scenario Creating a Persistent Storage when system is low on memory
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:16.084
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\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistence.feature:31:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And the system is very low on memory 0.000
When I create a file in the Persistent directory 0.000
When I try to create a persistent partition 0.000
Then The Persistent Storage app shows the error message "Not enough memory to create Persistent Storage" 0.000
When I close the Persistent Storage app 0.000
And I free up some memory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
After features/support/hooks.rb:330 5.386 
SCENARIO FAILED: 'Creating a Persistent Storage when system is low on memory' (at time 04:45:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:45:41_Creating_a_Persistent_Storage_when_system_is_low_on_memory.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:45:41_Creating_a_Persistent_Storage_when_system_is_low_on_memory.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:45:41_Creating_a_Persistent_Storage_when_system_is_low_on_memory.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:45:41_Creating_a_Persistent_Storage_when_system_is_low_on_memory.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:13.816
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 1:13.816
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:83: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 add a wired DHCP NetworkManager connection called "persistent-con-current" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
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.275 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:57:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:57:19_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:57:19_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:57:19_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:57:19_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:35.111
Scenario Creating persistence from the Welcome Screen
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 without a persistent partition and stopped at Tails Greeter's login screen 1:35.111
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\ without\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:97:in `Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen'
And I enable persistence creation in Tails Greeter 0.000
And I log in to a new session expecting no warning about the Persistent Storage not being activated 0.000
Then I create a persistent partition with the default settings using the wizard that was already open 0.000
After features/support/hooks.rb:330 5.613 
SCENARIO FAILED: 'Creating persistence from the Welcome Screen' (at time 04:59:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:59:02_Creating_persistence_from_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:59:02_Creating_persistence_from_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:59:02_Creating_persistence_from_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/04:59:02_Creating_persistence_from_the_Welcome_Screen.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:20.293
Scenario Changing the Persistent Storage passphrase
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 enabled and logged in 1:11.685
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 1:8.608
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:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:121:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 17.691 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 05:10:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:10:56_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:10:56_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:10:56_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
33.489
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.437
And I log in to a new session without activating the Persistent Storage 12.052
<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.433 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 05:11:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:11:42_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:11:42_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:11:42_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:11:42_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:19.816
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 19.381
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.125
When I try to enable persistence 0.305
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.003
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:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 20.506 
SCENARIO FAILED: 'Feature activation fails' (at time 05:17:40)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:17:40_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:17:40_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:17:40_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
7:32.380
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
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 7:32.380
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\ LUKS\ 1\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:154:in `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'
And I enable persistence 0.000
And I log in to a new session after having activated the Persistent Storage 0.000
Then a Tails persistence partition with LUKS version 2 and argon2id exists on USB drive "__internal" 0.000
And persistence is enabled 0.000
After features/support/hooks.rb:330 5.632 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 05:25:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:25:22_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:25:22_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:25:22_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:25:22_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:36.659
Scenario Manual filesystem repair is successful
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 and stopped at Tails Greeter's login screen 21.212
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 14.891
When I try to enable persistence 0.554
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.001
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:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 11.648 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 05:30:07)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:30:07_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:30:07_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:30:07_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:12.747
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.123
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 11.541
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.219
When I try to enable persistence 0.851
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.134
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:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 21.947 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:31:41)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:31:41_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:31:41_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:31:41_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:35.300
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
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.779
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 16.341
And Tails detects disk read failures on the boot device 1.742
When I try to enable persistence 0.433
Then the Welcome Screen tells me that my hardware is probably failing 1:0.003
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:1835:in `/^the Welcome Screen tells me that my hardware is probably failing$/'
features/persistence.feature:210:in `Then the Welcome Screen tells me that my hardware is probably failing'
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 15.911 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 05:33:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:33:36_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:33:36_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/05:33:36_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
54.968
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 18.037
When I start the Tor Browser 36.931
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/torified_browsing.feature:75:in `When I start the Tor Browser'
Then the Tor Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 6.062 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 06:21:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:21:02_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:21:02_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:21:02_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:21:02_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:22.274
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.171
And all tps features are active 2.982
And all persistent filesystems have safe access rights 0.765
And all persistence configuration files have safe access rights 1.209
And all persistent directories have safe access rights 6.979
When I start the Tor Browser in offline mode 42.053
And I add a bookmark to eff.org in the Tor Browser 12.112
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'click' action on [menu item | ]
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:368:in `click'
./features/step_definitions/browser.rb:509:in `/^I add a bookmark to eff.org in the Tor Browser$/'
features/torified_browsing.feature:140:in `And I add a bookmark to eff.org in the Tor Browser'
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 8.836 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 06:35:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:35:15_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:35:15_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:35:15_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:35:15_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
45.452
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 33.612
And I unlock and mount this VeraCrypt file container with GNOME Disks 11.840
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:68: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.848 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 06:58:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:58:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:58:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:58:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/2/artifact/build-artifacts/06:58:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015