Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 21 09 Jun 2026, 15: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 12:44.392 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:32.208
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.525
When I start Tails from USB drive "old" with network unplugged 1:12.278
Then the boot device has safe access rights 3.406
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:335 3.929
After features/support/hooks.rb:104 0.030
Tags: @product
1:41.711
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 1:1.717
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 29.578
And I take note of which tps features are available 0.510
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.792
After features/support/hooks.rb:335 0.209
After features/support/hooks.rb:104 0.009
Tags: @product
1:33.902
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.576
Then Tails is running from USB drive "old" 0.544
And all tps features are active 1.271
When I write some files expected to persist 1.490
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.199
And I take note of which tps features are available 0.211
And I shutdown Tails and wait for the computer to power off 6.835
# 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" 13.111
After features/support/hooks.rb:335 0.462
After features/support/hooks.rb:104 0.008
Tags: @product
2:17.914
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 9.243
And I log in to a new session 14.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.819
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.931
Then the running Tails is installed on USB drive "to_upgrade" 17.780
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.429
After features/support/hooks.rb:104 0.000
Tags: @product
1:18.174
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.166
Then all tps features from the old Tails version are active 1.267
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.587
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.296
After features/support/hooks.rb:335 0.614
After features/support/hooks.rb:104 0.027
Tags: @product @automatic_upgrade
3:58.139
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 with a persistent partition enabled and logged in 8.808
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.014
And Tor is ready 13.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.875
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.351
Given I shutdown Tails and wait for the computer to power off 7.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.644
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.335
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.237
When the network is plugged 0.019
And Tor is ready 11.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.750
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.104
Given I shutdown Tails and wait for the computer to power off 4.711
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.071
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.150
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.017
And Tor is ready 12.199
Then the Upgrader considers the system as up-to-date 10.597
# 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.622
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.570
After features/support/hooks.rb:335 0.848
After features/support/hooks.rb:104 0.026
Tags: @product @automatic_upgrade
22.341
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.064
After features/support/hooks.rb:335 0.981
After features/support/hooks.rb:104 0.000