Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 36 23 Jun 2026, 19:59

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:35.248 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:7.489
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.213
When I start Tails from USB drive "old" with network unplugged 49.901
Then the boot device has safe access rights 2.616
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:339 3.634
After features/support/hooks.rb:108 0.052
Tags: @product
1:29.717
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 53.600
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.712
And I take note of which tps features are available 3.734
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 7.834
After features/support/hooks.rb:339 0.176
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.436
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.907
Then Tails is running from USB drive "old" 0.237
And all tps features are active 4.692
When I write some files expected to persist 1.263
# 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.280
And all persistent directories from the old Tails version have safe access rights 1.789
And I take note of which tps features are available 3.518
And I shutdown Tails and wait for the computer to power off 7.856
# 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.685
After features/support/hooks.rb:339 0.392
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.772
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 without a persistent partition and stopped at Tails Greeter's login screen 8.285
And I log in to a new session 13.112
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.713
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.986
Then the running Tails is installed on USB drive "to_upgrade" 15.175
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.301
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.043
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.000
Then all tps features from the old Tails version are active 0.916
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.165
And all persistent directories from the old Tails version have safe access rights 1.744
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:40.076
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.101
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.015
And Tor is ready 12.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.322
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.890
Given I shutdown Tails and wait for the computer to power off 6.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.291
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 4.884
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.222
When the network is plugged 0.020
And Tor is ready 10.611
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.697
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.279
Given I shutdown Tails and wait for the computer to power off 4.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.079
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.669
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.012
And Tor is ready 10.623
Then the Upgrader considers the system as up-to-date 10.504
# 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.087
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 0.872
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.413
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.484
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.110
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.508
After features/support/hooks.rb:339 0.815
After features/support/hooks.rb:108 0.000