Project Number Date
test_Tails_ISO_21461-update-chutney 8 30 Jul 2026, 13:09

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:27.871 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:4.907
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.599
When I start Tails from USB drive "old" with network unplugged 46.936
Then the boot device has safe access rights 2.564
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.678
After features/support/hooks.rb:108 0.035
Tags: @product
1:26.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 52.669
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 24.675
And I take note of which tps features are available 4.194
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 4.049
After features/support/hooks.rb:339 0.405
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.852
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.238
Then Tails is running from USB drive "old" 0.238
And all tps features are active 4.434
When I write some files expected to persist 1.229
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 2.032
And I take note of which tps features are available 3.815
And I shutdown Tails and wait for the computer to power off 2.820
# 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.533
After features/support/hooks.rb:339 0.525
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.059
And I log in to a new session 12.468
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.897
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.161
Then the running Tails is installed on USB drive "to_upgrade" 14.562
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 2.029
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.260
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.635
Then all tps features from the old Tails version are active 0.822
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.020
And all persistent directories from the old Tails version have safe access rights 1.944
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.062
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 7.944
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.014
And Tor is ready 13.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.520
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.559
Given I shutdown Tails and wait for the computer to power off 5.412
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.427
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.937
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.187
When the network is plugged 0.016
And Tor is ready 9.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.969
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.191
Given I shutdown Tails and wait for the computer to power off 4.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.415
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.343
And the file system changes introduced in version 6.3~testoverlayfs are present 1.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.013
And Tor is ready 10.870
Then the Upgrader considers the system as up-to-date 10.535
# 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 4.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 0.899
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
27.694
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 7.330
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.776
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.277
After features/support/hooks.rb:339 1.028
After features/support/hooks.rb:108 0.000