Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 5 25 Jul 2024, 23:07

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Tails persistence 63 12 64 0 0 139 8 12 20 17:44.082 Failed
Tags: @product
Feature Tails persistence
As a Tails user I want to use a Persistent Storage
Tags: @product
2:23.257
Before features/support/hooks.rb:269 0.005
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:34.446
And I update APT using apt 19.764
And I install "python3-behave" using apt 25.770
Then the Tails Persistent Storage behave tests pass 3.276
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000
Tags: @product
41.883
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 11.992
When I log in to a new session without activating the Persistent Storage 23.359
Then Tails is running from USB drive "__internal" 0.389
And persistence is disabled 0.239
But a Tails persistence partition exists on USB drive "__internal" 5.902
After features/support/hooks.rb:326 1.086
After features/support/hooks.rb:100 0.000
Tags: @product
1:54.170
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 12.660
Then Tails is running from USB drive "__internal" 0.701
When I create a file in the Persistent directory 0.150
And I create a persistent partition with the default settings 25.653
Then the file I created was copied to the Persistent Storage 0.726
When I shutdown Tails and wait for the computer to power off 12.538
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.739
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:285: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/persistence.feature:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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:326 4.923 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 02:20:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:20:56_Creating_a_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:20:56_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:20:56_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:20:56_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.008
Tags: @product
58.198
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.622
And the system is very low on memory 5.514
When I create a file in the Persistent directory 1.742
When I try to create a persistent partition 24.153
Then The Persistent Storage app shows the error message "Not enough memory to create Persistent Storage" 0.127
When I close the Persistent Storage app 2.568
And I free up some memory 1.448
And I create a persistent partition with the default settings 11.771
Then the file I created was copied to the Persistent Storage 0.250
After features/support/hooks.rb:326 1.201
After features/support/hooks.rb:100 0.000
Tags: @product
14.489
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.489
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:42:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then Tails is running from USB drive "__internal" 0.000
And all tps features are active 0.000
And all persistent directories have safe access rights 0.000
When I disable the first tps feature 0.000
Then all tps features but the first one are active 0.000
And 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 all tps features but the first one are active 0.000
After features/support/hooks.rb:326 6.608 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 02:22:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:15_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:15_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:15_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:15_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.000
Tags: @product
12.882
Scenario Activating and deactivating Persistent Storage features
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.882
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:53:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
And I create a file in the Persistent directory 0.000
Then the file I created was copied to the Persistent Storage 0.000
When I disable the first tps feature 0.000
Then persistence for "Persistent" is not active 0.000
And the Persistent directory does not exist 0.000
When I enable the first tps feature 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:326 5.144 
SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 02:22:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:35_Activating_and_deactivating_Persistent_Storage_features.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:35_Activating_and_deactivating_Persistent_Storage_features.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:35_Activating_and_deactivating_Persistent_Storage_features.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:22:35_Activating_and_deactivating_Persistent_Storage_features.journal
After features/support/hooks.rb:100 0.000
Tags: @product
25.859
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.859
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
When I create a file in the Persistent directory 0.000
And I disable the first tps feature 0.000
And I delete the data of the Persistent Folder feature 0.000
Then the file I created does not exist on the Persistent Storage 0.000
After features/support/hooks.rb:326 5.698 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 02:23:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:06_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:06_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:06_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:06_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Tags: @product
12.004
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.004
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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:326 6.267 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 02:23:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:24_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_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:24_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:24_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:24_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Tags: @product
12.522
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.522
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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:326 5.387 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 02:23:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:42_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:42_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:42_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:23:42_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.498
Before features/support/hooks.rb:269 0.030
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.857
And I enable persistence creation in Tails Greeter 1.166
And I log in to a new session expecting no warning about the Persistent Storage not being activated 23.135
Then I create a persistent partition with the default settings using the wizard that was already open 24.338
After features/support/hooks.rb:326 1.559
After features/support/hooks.rb:100 0.000
Tags: @product
12.357
Scenario Persistent Greeter options
Before features/support/hooks.rb:269 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.444
When I enable persistence 2.913
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:104:in `When I enable persistence'
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:326 5.812 
SCENARIO FAILED: 'Persistent Greeter options' (at time 02:25:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:06_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:06_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:06_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:06_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Tags: @product
13.589
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.589
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:117:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# 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 0.000
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:326 5.416 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 02:25:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:26_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:26_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:26_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:25:26_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Tags: @product
51.364
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.301
And I log in to a new session without activating the Persistent Storage 19.327
Then persistence is disabled 0.254
But a Tails persistence partition exists on USB drive "__internal" 5.654
And all notifications have disappeared 9.846
When I delete the persistent partition 6.547
Then there is no persistence partition on USB drive "__internal" 0.432
After features/support/hooks.rb:326 2.176
After features/support/hooks.rb:100 0.000
Tags: @product
25.023
Scenario Dotfiles persistence
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.023
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And 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 the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:326 5.339 
SCENARIO FAILED: 'Dotfiles persistence' (at time 02:26:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:26:50_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:26:50_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:26:50_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:26:50_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Tags: @product
1:41.702
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.025
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.210
When I try to enable persistence 0.284
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 33.496
When I log in to a new session after having activated the Persistent Storage 41.028
And all notifications have disappeared 7.918
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 4.117
And all tps features are enabled 3.581
And all tps features but the first one are active 2.038
After features/support/hooks.rb:326 1.205
After features/support/hooks.rb:100 0.000
Tags: @product
4:41.091
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 4:38.167
And I enable persistence 2.924
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:155:in `And I enable persistence'
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:326 5.134 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 02:33:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:19_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_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:19_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:19_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:19_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Tags: @product
10.378
Scenario LUKS backup header is restored if something goes wrong during upgrade
Before features/support/hooks.rb:269 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 8.669
And I enable persistence but something goes wrong during the LUKS header upgrade 1.708
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:718:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:326 5.224 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 02:33:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:35_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:35_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:35_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:35_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product
19.028
Scenario Automatic filesystem repair
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.145
And I corrupt the Persistent Storage filesystem on USB drive "__internal" 6.010
When I enable persistence 3.873
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:691:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:168:in `When I enable persistence'
Then the filesystem of the Persistent Storage was repaired 0.000
After features/support/hooks.rb:326 5.388 
SCENARIO FAILED: 'Automatic filesystem repair' (at time 02:33:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:59_Automatic_filesystem_repair.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:59_Automatic_filesystem_repair.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:59_Automatic_filesystem_repair.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/5/artifact/build-artifacts/02:33:59_Automatic_filesystem_repair.journal
After features/support/hooks.rb:100 0.000
Tags: @product
25.010
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.719
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 5.646
When I try to enable persistence 0.433
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 6.417
When I repair the filesystem of the Persistent Storage 1.266
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.233
And the filesystem of the Persistent Storage was repaired 0.103
When I close the filesystem repair dialog 1.307
Then persistence is successfully enabled 0.881
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.000
Tags: @product
24.770
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.005
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 9.748
And Tails detects disk read failures on the boot device 0.454
When I try to enable persistence 0.456
Then the Welcome Screen tells me that my hardware is probably failing 5.104
After features/support/hooks.rb:326 1.059
After features/support/hooks.rb:100 0.000