Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 44 01 Jul 2026, 20:08

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:55.823 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:9.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.199
When I start Tails from USB drive "old" with network unplugged 52.130
Then the boot device has safe access rights 2.417
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:339 3.501
After features/support/hooks.rb:108 0.042
Tags: @product
1:29.406
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 54.056
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 25.499
And I take note of which tps features are available 4.834
Then a Tails persistence partition exists on USB drive "old" 0.651
And I shutdown Tails and wait for the computer to power off 4.085
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.808
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.914
Then Tails is running from USB drive "old" 0.235
And all tps features are active 4.710
When I write some files expected to persist 1.187
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.264
And all persistent directories from the old Tails version have safe access rights 2.426
And I take note of which tps features are available 4.338
And I shutdown Tails and wait for the computer to power off 8.173
# 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.349
After features/support/hooks.rb:339 0.574
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.649
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.462
And I log in to a new session 14.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.817
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.119
Then the running Tails is installed on USB drive "to_upgrade" 15.655
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.576
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.529
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.978
Then all tps features from the old Tails version are active 0.921
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.309
And the expected persistent files created with the old Tails version are present in the filesystem 1.158
And all persistent directories from the old Tails version have safe access rights 1.854
After features/support/hooks.rb:339 0.867
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:51.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.579
And no SquashFS delta is installed 0.057
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.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.015
And Tor is ready 14.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.620
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.746
Given I shutdown Tails and wait for the computer to power off 6.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.297
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.054
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.224
When the network is plugged 0.018
And Tor is ready 11.038
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.574
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.171
Given I shutdown Tails and wait for the computer to power off 3.983
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.332
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.263
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.014
And Tor is ready 10.070
Then the Upgrader considers the system as up-to-date 10.559
# 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.202
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.411
After features/support/hooks.rb:339 0.996
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.405
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 8.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.121
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.000