Project Number Date
test_Tails_ISO_test-suite-options 24 09 Jul 2025, 05:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 2 10 0 0 87 5 2 7 33:22.453 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
3:18.699
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.299
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.120
And I write an old version of the Tails USB image to disk "old" 51.722
When I start Tails from USB drive "old" with network unplugged 2:20.862
Then the boot device has safe access rights 3.294
And Tails is running from USB drive "old" 0.457
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.140
And udev-watchdog is monitoring the correct device 0.409
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 3.983
After features/support/hooks.rb:100 0.072
Tags: @product
3:29.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.054
Given a computer 0.807
And I start Tails from USB drive "old" with network unplugged and I login 2:28.935
Then Tails is running from USB drive "old" 1.160
And I create a persistent partition 42.426
And I take note of which tps features are available 2.287
Then a Tails persistence partition exists on USB drive "old" 1.259
And I shutdown Tails and wait for the computer to power off 13.051
After features/support/hooks.rb:330 0.421
After features/support/hooks.rb:100 0.010
Tags: @product
4:59.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:41.512
Then Tails is running from USB drive "old" 0.596
And all tps features are active 2.233
When I write some files expected to persist 2.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.303
And all persistence configuration files have safe access rights 0.621
And all persistent directories from the old Tails version have safe access rights 8.167
And I take note of which tps features are available 0.931
And I shutdown Tails and wait for the computer to power off 7.115
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 55.791
After features/support/hooks.rb:330 0.910
After features/support/hooks.rb:100 0.038
Tags: @product
4:42.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 31.328
And I log in to a new session 35.735
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.363
And I plug USB drive "to_upgrade" 8.338
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:17.385
Then the running Tails is installed on USB drive "to_upgrade" 1:3.183
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.280
After features/support/hooks.rb:330 12.728
After features/support/hooks.rb:100 0.000
Tags: @product
4:10.969
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Given a computer 0.824
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:48.130
Then all tps features from the old Tails version are active 2.782
And Tails is running from USB drive "to_upgrade" 0.416
And the boot device has safe access rights 13.892
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 3.481
After features/support/hooks.rb:330 1.208
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
11:30.356
Scenario Upgrading an initial Tails installation with an incremental upgrade
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 enabled and logged in 30.696
And no SquashFS delta is installed 0.309
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.655
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.255
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.576
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.839
When the network is plugged 0.092
And Tor is ready 40.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.438
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.372
Given I shutdown Tails and wait for the computer to power off 17.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:44.404
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.431
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.198
And Tor is ready 34.435
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 19.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 24.367
Given I shutdown Tails and wait for the computer to power off 13.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:24.093
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.878
And the file system changes introduced in version 6.3~testoverlayfs are present 5.755
And only the 6.3~testoverlayfs SquashFS delta is installed 1.434
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.970
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.836
When the network is plugged 1.135
And Tor is ready 18.801
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:119:in `And Tor is ready'
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.110 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:23:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.062
Tags: @product @automatic_upgrade
1:9.955
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.086
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:9.955
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/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 8.518 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:24:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000