Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 101 24 Jun 2025, 21:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Tails persistence 84 10 63 0 0 157 11 10 21 57:16.415 Failed
Tags: @product
Feature Tails persistence
As a Tails user I want to use a Persistent Storage
Tags: @product
5:59.815
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given I have started Tails from DVD and logged in with an administration password and the network is connected 4:38.456
And I update APT using apt 30.083
And I install "python3-behave" using apt 44.192
Then the Tails Persistent Storage behave tests pass 7.083
After features/support/hooks.rb:335 0.925
After features/support/hooks.rb:105 0.000
Tags: @product
35.885
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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 23.680
When I log in to a new session without activating the Persistent Storage 12.204
<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:335 5.479 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 04:42:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:42:27_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:42:27_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:42:27_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:42:27_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:105 0.000
Tags: @product
6:42.835
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Given I have started Tails without network from a USB drive without a persistent partition and logged in 22.726
Then Tails is running from USB drive "__internal" 0.421
When I create a file in the Persistent directory 0.140
And I create a persistent partition with the default settings 59.854
Then the file I created was copied to the Persistent Storage 4.805
When I shutdown Tails and wait for the computer to power off 16.115
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:58.113
Then persistence for "Persistent" is active 0.570
And the file I created in the Persistent directory exists 0.087
After features/support/hooks.rb:335 4.894
After features/support/hooks.rb:105 0.031
Tags: @product
1:27.691
Scenario Creating a Persistent Storage when system is low on memory
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.020
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:27.691
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:335 6.227 
SCENARIO FAILED: 'Creating a Persistent Storage when system is low on memory' (at time 04:50:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:50:49_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:50:49_Creating_a_Persistent_Storage_when_system_is_low_on_memory.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:50:49_Creating_a_Persistent_Storage_when_system_is_low_on_memory.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:50:49_Creating_a_Persistent_Storage_when_system_is_low_on_memory.journal
After features/support/hooks.rb:105 0.000
Tags: @product
1:33.067
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:33.067
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: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:335 7.177 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 04:52:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:52:28_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:52:28_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:52:28_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:52:28_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:105 0.000
Tags: @product
43.949
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.704
Then persistence for "Persistent" is active 0.064
And I create a file in the Persistent directory 0.214
Then the file I created was copied to the Persistent Storage 0.132
When I disable the first tps feature 16.204
Then persistence for "Persistent" is not active 0.366
And the Persistent directory does not exist 0.130
When I enable the first tps feature 4.172
Then persistence for "Persistent" is active 0.648
And the file I created in the Persistent directory exists 1.310
After features/support/hooks.rb:335 4.639
After features/support/hooks.rb:105 0.000
Tags: @product
1:41.069
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.633
Then persistence for "Persistent" is active 3.008
When I create a file in the Persistent directory 0.976
And I disable the first tps feature 8.412
And I delete the data of the Persistent Folder feature 10.511
Then the file I created does not exist on the Persistent Storage 1.525
After features/support/hooks.rb:335 3.324
After features/support/hooks.rb:105 0.000
Tags: @product
1:16.775
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.775
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:335 7.206 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 04:56:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:56:25_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:56:25_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:56:25_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:56:25_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:105 0.000
Tags: @product
1:15.385
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.385
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:335 6.738 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:57:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:57:48_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:57:48_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:57:48_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/04:57:48_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:105 0.000
Tags: @product
2:1.097
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 27.364
And I enable persistence creation in Tails Greeter 1.413
And I log in to a new session expecting no warning about the Persistent Storage not being activated 43.073
Then I create a persistent partition with the default settings using the wizard that was already open 49.245
After features/support/hooks.rb:335 8.370
After features/support/hooks.rb:105 0.000
Tags: @product
9:2.146
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 54.511
When I enable persistence 1:31.625
Then no persistent Greeter options were restored 18.175
When I set all Greeter options to non-default values 58.301
And I log in to a new session in German (de) after having activated the Persistent Storage 1:11.488
Then all Greeter options are set to non-default values 8.570
When I cold reboot the computer 18.601
And the computer reboots Tails 1:48.167
Given I enable persistence 37.347
Then persistent Greeter options were restored 0.676
When I log in to a new session after having activated the Persistent Storage 1:10.059
Then all Greeter options are set to non-default values 4.621
After features/support/hooks.rb:335 4.819
After features/support/hooks.rb:105 0.009
Tags: @product
1:17.579
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.579
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: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:335 6.573 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 05:10:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:10:29_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:10:29_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:10:29_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:10:29_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:105 0.000
Tags: @product
31.842
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
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.919
And I log in to a new session without activating the Persistent Storage 11.922
<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:335 5.740 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 05:11:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:11:07_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:11:07_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:11:07_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:11:07_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:105 0.000
Tags: @product
4:50.107
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.759
When I write some dotfile expected to persist 0.116
And I shutdown Tails and wait for the computer to power off 18.114
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:5.850
Then the expected persistent dotfile is present in the filesystem 4.267
After features/support/hooks.rb:335 4.401
After features/support/hooks.rb:105 0.043
Tags: @product
1:15.387
Scenario Feature activation fails
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
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.983
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.905
When I try to enable persistence 2.346
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.151
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:335 15.900 
SCENARIO FAILED: 'Feature activation fails' (at time 05:17:26)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:17:26_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:17:26_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:17:26_Feature_activation_fails.journal
After features/support/hooks.rb:105 0.000
Tags: @product
6:6.049
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.046
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 6:6.049
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:335 5.859 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 05:23:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:23:47_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_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:23:47_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:23:47_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:23:47_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:105 0.000
Tags: @product
1:13.361
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.015
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 28.585
And I enable persistence but something goes wrong during the LUKS header upgrade 40.459
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 4.316
After features/support/hooks.rb:335 1.908
After features/support/hooks.rb:105 0.000
Tags: @product
2:44.705
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:11.740
And I corrupt the Persistent Storage filesystem on USB drive "__internal" 11.358
When I enable persistence 1:17.871
Then the filesystem of the Persistent Storage was repaired 0.104
And persistence is successfully enabled 3.630
After features/support/hooks.rb:335 2.604
After features/support/hooks.rb:105 0.000
Tags: @product
1:54.322
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 20.331
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 15.683
When I try to enable persistence 0.589
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 58.501
When I repair the filesystem of the Persistent Storage 1.320
Then the Welcome Screen tells me that the filesystem was repaired successfully 4.860
And the filesystem of the Persistent Storage was repaired 7.891
When I close the filesystem repair dialog 3.510
Then persistence is successfully enabled 1.634
After features/support/hooks.rb:335 1.197
After features/support/hooks.rb:105 0.000
Tags: @product @doc
1:32.738
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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 30.762
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.819
When I try to enable persistence 1.123
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.032
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:335 17.180 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:31:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:31:28_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:31:28_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/05:31:28_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:105 0.000
Tags: @product @doc
3:30.603
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.123
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 15.733
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 11.247
And Tails detects disk read failures on the boot device 1.901
When I try to enable persistence 0.539
Then the Welcome Screen tells me that my hardware is probably failing 47.700
When I log in to a new session 1:11.852
And all notifications have disappeared 18.640
Then the Tor Browser starts 40.876
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 2.111
After features/support/hooks.rb:335 7.972
After features/support/hooks.rb:105 0.000