Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 33 20 Jun 2026, 20:09

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:59.728 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:20.954
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.504
When I start Tails from USB drive "old" with network unplugged 1:2.790
Then the boot device has safe access rights 2.811
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 3.605
After features/support/hooks.rb:108 0.054
Tags: @product
1:31.991
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login 55.255
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 24.707
And I take note of which tps features are available 3.961
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 6.907
After features/support/hooks.rb:339 0.362
After features/support/hooks.rb:108 0.018
Tags: @product
1:31.510
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.726
Then Tails is running from USB drive "old" 0.237
And all tps features are active 4.576
When I write some files expected to persist 1.111
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.283
And all persistent directories from the old Tails version have safe access rights 2.028
And I take note of which tps features are available 3.810
And I shutdown Tails and wait for the computer to power off 2.806
# 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" 11.651
After features/support/hooks.rb:339 0.316
After features/support/hooks.rb:108 0.018
Tags: @product
2:12.543
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.032
And I log in to a new session 14.085
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.770
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.198
Then the running Tails is installed on USB drive "to_upgrade" 14.986
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.547
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.597
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.750
Then all tps features from the old Tails version are active 1.071
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.405
And the expected persistent files created with the old Tails version are present in the filesystem 1.086
And all persistent directories from the old Tails version have safe access rights 1.923
After features/support/hooks.rb:339 0.627
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
3:48.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.272
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
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.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.014
And Tor is ready 12.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.544
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.024
Given I shutdown Tails and wait for the computer to power off 6.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.495
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.230
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.191
When the network is plugged 0.018
And Tor is ready 9.776
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.654
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.496
Given I shutdown Tails and wait for the computer to power off 4.102
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.078
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.904
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.013
And Tor is ready 10.964
Then the Upgrader considers the system as up-to-date 10.520
# 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.865
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
21.071
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.577
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 9.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.303
After features/support/hooks.rb:339 0.663
After features/support/hooks.rb:108 0.000