Project Number Date
test_Tails_ISO_21769-gather-chutney-configure-backtrace-take-2 1 14 Sep 2026, 19:51

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:38.748 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:8.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.465
When I start Tails from USB drive "old" with network unplugged 49.936
Then the boot device has safe access rights 2.558
And Tails is running from USB drive "old" 0.183
And there is no persistence partition on USB drive "old" 0.028
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.487
After features/support/hooks.rb:108 0.032
Tags: @product
1:28.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.132
And I start Tails from USB drive "old" with network unplugged and I login 51.622
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 23.843
And I take note of which tps features are available 7.381
Then a Tails persistence partition exists on USB drive "old" 0.684
And I shutdown Tails and wait for the computer to power off 4.282
After features/support/hooks.rb:339 0.179
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.190
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.147
Then Tails is running from USB drive "old" 0.168
And all tps features are active 7.883
When I write some files expected to persist 1.404
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.117
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.791
And I take note of which tps features are available 6.628
And I shutdown Tails and wait for the computer to power off 2.565
# 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.101
After features/support/hooks.rb:339 0.176
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.176
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 without a persistent partition and stopped at Tails Greeter's login screen 8.855
And I log in to a new session 13.123
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.760
And I plug USB drive "to_upgrade" 2.196
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.718
Then the running Tails is installed on USB drive "to_upgrade" 18.278
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.234
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.223
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.164
Then all tps features from the old Tails version are active 1.006
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.128
And the expected persistent files created with the old Tails version are present in the filesystem 0.973
And all persistent directories from the old Tails version have safe access rights 1.656
After features/support/hooks.rb:339 0.523
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.852
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.319
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.186
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.035
And Tor is ready 13.041
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.861
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.828
Given I shutdown Tails and wait for the computer to power off 5.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.952
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.016
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
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.119
# 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.169
When the network is plugged 0.037
And Tor is ready 10.371
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.976
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.107
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.739
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.059
And Tor is ready 10.615
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.212
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:339 1.019
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
20.448
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.382
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 10.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.691
After features/support/hooks.rb:339 0.963
After features/support/hooks.rb:108 0.000