Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 6 02 Jun 2026, 15:02

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:25.801 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:7.868
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.049
When I start Tails from USB drive "old" with network unplugged 49.156
Then the boot device has safe access rights 2.739
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 3.762
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.310
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 53.945
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 25.347
And I take note of which tps features are available 0.344
Then a Tails persistence partition exists on USB drive "old" 0.587
And I shutdown Tails and wait for the computer to power off 6.757
After features/support/hooks.rb:335 0.556
After features/support/hooks.rb:104 0.008
Tags: @product
1:28.308
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.873
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.211
When I write some files expected to persist 1.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.131
And I take note of which tps features are available 0.201
And I shutdown Tails and wait for the computer to power off 7.056
# 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.660
After features/support/hooks.rb:335 0.539
After features/support/hooks.rb:104 0.010
Tags: @product
2:13.790
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.990
And I log in to a new session 12.855
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.043
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.623
Then the running Tails is installed on USB drive "to_upgrade" 16.733
And I unplug USB drive "to_upgrade" 0.169
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 2.621
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.523
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.830
Then all tps features from the old Tails version are active 1.146
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.834
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.074
After features/support/hooks.rb:335 0.763
After features/support/hooks.rb:104 0.013
3:36.408
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.011
And no SquashFS delta is installed 0.061
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.025
And Tor is ready 12.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.078
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.050
Given I shutdown Tails and wait for the computer to power off 7.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.375
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.195
When the network is plugged 0.018
And Tor is ready 10.826
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.812
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.687
Given I shutdown Tails and wait for the computer to power off 4.278
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.178
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.232
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.015
And Tor is ready 10.010
Then the Upgrader considers the system as up-to-date 10.606
# 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.677
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.441
After features/support/hooks.rb:335 0.951
After features/support/hooks.rb:104 0.013
20.592
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.370
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.510
After features/support/hooks.rb:335 0.724
After features/support/hooks.rb:104 0.000