Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 47 27 May 2026, 11:44

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 12:16.989 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:16.627
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.417
When I start Tails from USB drive "old" with network unplugged 56.528
Then the boot device has safe access rights 3.623
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:335 3.777
After features/support/hooks.rb:104 0.013
Tags: @product
1:36.735
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given a computer 0.151
And I start Tails from USB drive "old" with network unplugged and I login 1:0.385
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 26.314
And I take note of which tps features are available 0.381
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 8.653
After features/support/hooks.rb:335 0.302
After features/support/hooks.rb:104 0.009
Tags: @product
1:31.705
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.901
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.195
When I write some files expected to persist 1.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 2.054
And I take note of which tps features are available 0.211
And I shutdown Tails and wait for the computer to power off 8.580
# 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.591
After features/support/hooks.rb:335 0.143
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.410
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.368
And I log in to a new session 13.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.171
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.288
Then the running Tails is installed on USB drive "to_upgrade" 17.505
And I unplug USB drive "to_upgrade" 0.165
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.247
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.882
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.508
Then all tps features from the old Tails version are active 1.171
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.101
And the expected persistent files created with the old Tails version are present in the filesystem 1.318
And all persistent directories from the old Tails version have safe access rights 2.389
After features/support/hooks.rb:335 0.895
After features/support/hooks.rb:104 0.011
4:0.759
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.413
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.015
And Tor is ready 13.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.112
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.657
Given I shutdown Tails and wait for the computer to power off 9.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.185
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 1.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# 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.196
When the network is plugged 0.016
And Tor is ready 11.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.933
Given I shutdown Tails and wait for the computer to power off 8.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.496
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.693
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.026
And Tor is ready 11.582
Then the Upgrader considers the system as up-to-date 10.674
# 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 5.166
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:335 0.702
After features/support/hooks.rb:104 0.021
21.868
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 11.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.614
After features/support/hooks.rb:335 0.923
After features/support/hooks.rb:104 0.000