Project Number Date
test_Tails_ISO_21322-change-domain-deb.tails.boum.org 5 21 May 2026, 07: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:48.947 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:17.702
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.443
When I start Tails from USB drive "old" with network unplugged 59.572
Then the boot device has safe access rights 2.969
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:335 3.454
After features/support/hooks.rb:104 0.095
Tags: @product
1:28.646
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.014
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 54.661
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 24.469
And I take note of which tps features are available 0.332
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:335 0.309
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.543
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.902
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.486
When I write some files expected to persist 1.429
# 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.355
And all persistent directories from the old Tails version have safe access rights 2.066
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.261
# 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" 12.378
After features/support/hooks.rb:335 0.306
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.640
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.961
And I log in to a new session 12.852
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.788
And I plug USB drive "to_upgrade" 2.300
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.550
Then the running Tails is installed on USB drive "to_upgrade" 15.909
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 0.767
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.132
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.653
Then all tps features from the old Tails version are active 1.092
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.796
And the expected persistent files created with the old Tails version are present in the filesystem 1.131
And all persistent directories from the old Tails version have safe access rights 2.101
After features/support/hooks.rb:335 0.638
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:52.864
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.285
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.391
When the network is plugged 0.014
And Tor is ready 12.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.343
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.594
Given I shutdown Tails and wait for the computer to power off 9.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.810
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.205
When the network is plugged 0.020
And Tor is ready 11.519
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.595
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.349
Given I shutdown Tails and wait for the computer to power off 17.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.818
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.024
And Tor is ready 12.027
Then the Upgrader considers the system as up-to-date 10.515
# 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.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:335 1.089
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
19.418
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.854
After features/support/hooks.rb:335 0.800
After features/support/hooks.rb:104 0.000