Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 18 08 Jun 2026, 19:37

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:48.065 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.037
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.390
When I start Tails from USB drive "old" with network unplugged 1:2.936
Then the boot device has safe access rights 2.860
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:335 1.539
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.850
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 56.010
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 26.463
And I take note of which tps features are available 0.397
Then a Tails persistence partition exists on USB drive "old" 0.636
And I shutdown Tails and wait for the computer to power off 6.982
After features/support/hooks.rb:335 0.566
After features/support/hooks.rb:104 0.030
Tags: @product
1:26.861
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.538
Then Tails is running from USB drive "old" 0.242
And all tps features are active 1.160
When I write some files expected to persist 1.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.282
And all persistent directories from the old Tails version have safe access rights 1.988
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.019
# 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.068
After features/support/hooks.rb:335 0.440
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.488
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 without a persistent partition and stopped at Tails Greeter's login screen 8.569
And I log in to a new session 12.197
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.920
Then the running Tails is installed on USB drive "to_upgrade" 16.404
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:335 2.458
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.390
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.723
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.917
And the expected persistent files created with the old Tails version are present in the filesystem 1.237
And all persistent directories from the old Tails version have safe access rights 2.153
After features/support/hooks.rb:335 0.962
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:42.263
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.820
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.016
And Tor is ready 13.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.813
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.614
Given I shutdown Tails and wait for the computer to power off 7.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.820
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.189
When the network is plugged 0.017
And Tor is ready 10.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.730
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.205
Given I shutdown Tails and wait for the computer to power off 3.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.122
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.448
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.038
And Tor is ready 11.788
Then the Upgrader considers the system as up-to-date 10.544
# 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.422
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.458
After features/support/hooks.rb:335 0.721
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.173
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.018
And Tor is ready 10.093
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.545
After features/support/hooks.rb:335 1.053
After features/support/hooks.rb:104 0.000