Project Number Date
test_Tails_ISO_21769-fix-chutney-configure-freeze 1 30 Sep 2026, 17:50

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:57.459 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:22.708
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.409
When I start Tails from USB drive "old" with network unplugged 1:4.430
Then the boot device has safe access rights 2.115
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.112
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 49.240
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 23.866
And I take note of which tps features are available 6.912
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 3.847
After features/support/hooks.rb:339 0.152
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.731
Then Tails is running from USB drive "old" 0.270
And all tps features are active 8.167
When I write some files expected to persist 1.286
# 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.320
And all persistent directories from the old Tails version have safe access rights 1.883
And I take note of which tps features are available 6.828
And I shutdown Tails and wait for the computer to power off 3.904
# 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.847
After features/support/hooks.rb:339 0.305
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.874
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.995
And I log in to a new session 12.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.835
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.776
Then the running Tails is installed on USB drive "to_upgrade" 18.681
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 3.738
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.898
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.751
Then all tps features from the old Tails version are active 1.186
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.517
And the expected persistent files created with the old Tails version are present in the filesystem 1.013
And all persistent directories from the old Tails version have safe access rights 2.079
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.543
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 with a persistent partition enabled and logged in 8.249
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.039
And Tor is ready 13.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.291
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.235
Given I shutdown Tails and wait for the computer to power off 5.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.742
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 8.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.243
When the network is plugged 0.028
And Tor is ready 10.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.340
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.067
Given I shutdown Tails and wait for the computer to power off 3.918
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.010
And all tps features are active 8.774
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.046
And Tor is ready 10.826
Then the Upgrader considers the system as up-to-date 10.441
# 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.421
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.770
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.244
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.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 10.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.339
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.000