Project Number Date
test_Tails_ISO_codespell 10 24 Jun 2025, 12:49

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 79 1 7 0 0 87 6 1 7 38:5.203 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
4:21.138
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 1:2.085
When I start Tails from USB drive "old" with network unplugged 3:1.358
Then the boot device has safe access rights 15.120
And Tails is running from USB drive "old" 0.462
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:330 3.789
After features/support/hooks.rb:100 0.044
Tags: @product
4:15.322
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.401
And I start Tails from USB drive "old" with network unplugged and I login 2:55.220
Then Tails is running from USB drive "old" 0.586
And I create a persistent partition 1:1.056
And I take note of which tps features are available 3.115
Then a Tails persistence partition exists on USB drive "old" 1.089
And I shutdown Tails and wait for the computer to power off 13.852
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.013
Tags: @product
5:57.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:25.323
Then Tails is running from USB drive "old" 0.562
And all tps features are active 10.956
When I write some files expected to persist 2.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 3.281
And I take note of which tps features are available 0.650
And I shutdown Tails and wait for the computer to power off 12.739
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:0.513
After features/support/hooks.rb:330 0.225
After features/support/hooks.rb:100 0.027
Tags: @product
4:40.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 37.528
And I log in to a new session 36.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.695
And I plug USB drive "to_upgrade" 2.847
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:16.459
Then the running Tails is installed on USB drive "to_upgrade" 52.185
And I unplug USB drive "to_upgrade" 6.104
And I unplug USB drive "__internal" 1.407
After features/support/hooks.rb:330 3.644
After features/support/hooks.rb:100 0.000
Tags: @product
4:39.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 0.394
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:9.737
Then all tps features from the old Tails version are active 6.043
And Tails is running from USB drive "to_upgrade" 0.598
And the boot device has safe access rights 5.901
And the expected persistent files created with the old Tails version are present in the filesystem 10.886
And all persistent directories from the old Tails version have safe access rights 5.948
After features/support/hooks.rb:330 2.055
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
12:40.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.835
And no SquashFS delta is installed 3.586
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 4.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.797
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.644
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.876
When the network is plugged 0.097
And Tor is ready 43.093
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 16.670
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 24.057
Given I shutdown Tails and wait for the computer to power off 20.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:0.877
Then Tails is running version 6.2~testoverlayfs 0.094
And all tps features are active 6.353
And the file system changes introduced in version 6.2~testoverlayfs are present 3.395
And only the 6.2~testoverlayfs SquashFS delta is installed 0.303
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.786
# 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 2.666
When the network is plugged 0.323
And Tor is ready 36.725
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.345
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 24.332
Given I shutdown Tails and wait for the computer to power off 13.600
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:41.668
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 3.406
And the file system changes introduced in version 6.3~testoverlayfs are present 0.649
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.558
When the network is plugged 5.281
And Tor is ready 26.901
Then the Upgrader considers the system as up-to-date 0.326
# 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 23.844
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.579
After features/support/hooks.rb:330 0.843
After features/support/hooks.rb:100 0.352
Tags: @product @automatic_upgrade
1:29.858
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.225
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.858
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 7.481 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:19:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000