Project Number Date
test_Tails_ISO_21461-update-chutney 16 07 Aug 2026, 22:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:31.727 Passed
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
1:15.035
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.278
When I start Tails from USB drive "old" with network unplugged 57.929
Then the boot device has safe access rights 2.162
And Tails is running from USB drive "old" 0.171
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 1.080
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 47.483
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.209
And I take note of which tps features are available 6.588
Then a Tails persistence partition exists on USB drive "old" 0.486
And I shutdown Tails and wait for the computer to power off 2.548
After features/support/hooks.rb:339 0.194
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.712
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.922
Then Tails is running from USB drive "old" 0.201
And all tps features are active 6.720
When I write some files expected to persist 1.468
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.644
And I take note of which tps features are available 6.134
And I shutdown Tails and wait for the computer to power off 2.581
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.481
After features/support/hooks.rb:339 0.555
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.580
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.108
And I log in to a new session 10.968
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.190
Then the running Tails is installed on USB drive "to_upgrade" 18.219
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 6.694
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.594
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.332
Then all tps features from the old Tails version are active 1.165
And Tails is running from USB drive "to_upgrade" 0.175
And the boot device has safe access rights 2.089
And the expected persistent files created with the old Tails version are present in the filesystem 1.082
And all persistent directories from the old Tails version have safe access rights 1.666
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.009
3:46.982
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.015
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.165
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.025
And Tor is ready 13.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.399
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.981
Given I shutdown Tails and wait for the computer to power off 5.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.258
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.858
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.087
# 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.172
When the network is plugged 0.028
And Tor is ready 14.237
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.819
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.418
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 7.689
And the file system changes introduced in version 6.3~testoverlayfs are present 0.299
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.032
And Tor is ready 11.344
Then the Upgrader considers the system as up-to-date 0.090
# 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 3.132
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:339 0.829
After features/support/hooks.rb:108 0.008
20.183
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.202
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.000