Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 13 04 Jun 2026, 20:03

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:46.835 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:25.437
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.539
When I start Tails from USB drive "old" with network unplugged 1:7.378
Then the boot device has safe access rights 2.723
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:335 3.677
After features/support/hooks.rb:104 0.040
Tags: @product
1:32.246
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 56.971
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 25.770
And I take note of which tps features are available 0.338
Then a Tails persistence partition exists on USB drive "old" 0.721
And I shutdown Tails and wait for the computer to power off 8.142
After features/support/hooks.rb:335 0.155
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.675
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.093
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.041
When I write some files expected to persist 1.262
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 1.955
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 4.202
# 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.126
After features/support/hooks.rb:335 0.158
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.900
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 without a persistent partition and stopped at Tails Greeter's login screen 8.646
And I log in to a new session 12.543
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.965
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.205
Then the running Tails is installed on USB drive "to_upgrade" 15.984
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:335 2.310
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.912
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.636
Then all tps features from the old Tails version are active 0.967
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.532
And the expected persistent files created with the old Tails version are present in the filesystem 1.284
And all persistent directories from the old Tails version have safe access rights 2.168
After features/support/hooks.rb:335 0.863
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:40.277
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 8.151
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.016
And Tor is ready 12.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.326
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.776
Given I shutdown Tails and wait for the computer to power off 6.762
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.667
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.235
When the network is plugged 0.017
And Tor is ready 11.286
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.472
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.780
Given I shutdown Tails and wait for the computer to power off 4.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.554
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.230
When the network is plugged 0.026
And Tor is ready 11.064
Then the Upgrader considers the system as up-to-date 10.612
# 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.626
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:335 0.756
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.383
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 7.484
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.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.015
And Tor is ready 9.942
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.575
After features/support/hooks.rb:335 0.861
After features/support/hooks.rb:104 0.000