Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 1 17 Aug 2026, 19:47

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:26.638 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:9.626
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.807
When I start Tails from USB drive "old" with network unplugged 51.420
Then the boot device has safe access rights 2.397
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.287
After features/support/hooks.rb:339 3.423
After features/support/hooks.rb:108 0.045
Tags: @product
1:26.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 51.364
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.415
And I take note of which tps features are available 7.037
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 4.202
After features/support/hooks.rb:339 0.511
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.848
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.980
Then Tails is running from USB drive "old" 0.193
And all tps features are active 7.353
When I write some files expected to persist 1.093
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.885
And I take note of which tps features are available 6.644
And I shutdown Tails and wait for the computer to power off 2.554
# 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.554
After features/support/hooks.rb:339 0.506
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.575
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.702
And I log in to a new session 12.822
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.584
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.750
Then the running Tails is installed on USB drive "to_upgrade" 18.247
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 3.915
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.856
Then all tps features from the old Tails version are active 1.203
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.239
And the expected persistent files created with the old Tails version are present in the filesystem 1.008
And all persistent directories from the old Tails version have safe access rights 1.657
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.008
3:32.837
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.626
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.024
And Tor is ready 12.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.664
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.328
Given I shutdown Tails and wait for the computer to power off 6.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.048
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.405
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.165
When the network is plugged 0.025
And Tor is ready 10.317
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.601
Given I shutdown Tails and wait for the computer to power off 2.630
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.247
Then Tails is running version 6.3~testoverlayfs 0.044
And all tps features are active 7.617
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.075
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.025
And Tor is ready 10.426
Then the Upgrader considers the system as up-to-date 0.088
# 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.466
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.337
After features/support/hooks.rb:339 0.963
After features/support/hooks.rb:108 0.009
19.608
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.716
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.173
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.739
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.834
After features/support/hooks.rb:339 0.569
After features/support/hooks.rb:108 0.000