Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 49 06 Jul 2026, 20: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:36.030 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:6.309
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.274
When I start Tails from USB drive "old" with network unplugged 48.494
Then the boot device has safe access rights 2.715
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:339 3.794
After features/support/hooks.rb:108 0.052
Tags: @product
1:30.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 53.060
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 24.435
And I take note of which tps features are available 3.986
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 7.910
After features/support/hooks.rb:339 0.176
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.724
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.444
Then Tails is running from USB drive "old" 0.293
And all tps features are active 4.977
When I write some files expected to persist 1.216
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.903
And I take note of which tps features are available 3.562
And I shutdown Tails and wait for the computer to power off 7.921
# 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.883
After features/support/hooks.rb:339 0.102
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.202
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.419
And I log in to a new session 11.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.722
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.519
Then the running Tails is installed on USB drive "to_upgrade" 15.264
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:339 2.579
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.984
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.336
Then all tps features from the old Tails version are active 0.890
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.525
And the expected persistent files created with the old Tails version are present in the filesystem 1.103
And all persistent directories from the old Tails version have safe access rights 1.859
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.884
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.349
And no SquashFS delta is installed 0.075
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.015
And Tor is ready 13.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.058
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.436
Given I shutdown Tails and wait for the computer to power off 6.733
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.958
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.800
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.219
When the network is plugged 0.016
And Tor is ready 10.779
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.540
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.472
Given I shutdown Tails and wait for the computer to power off 4.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.072
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.457
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.015
And Tor is ready 10.531
Then the Upgrader considers the system as up-to-date 10.489
# 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.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:339 1.063
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.758
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 with a persistent partition enabled and logged in 7.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.731
After features/support/hooks.rb:339 1.021
After features/support/hooks.rb:108 0.000