Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 55 14 Jul 2026, 00: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:45.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:20.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 12.779
When I start Tails from USB drive "old" with network unplugged 1:3.076
Then the boot device has safe access rights 2.743
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 4.056
After features/support/hooks.rb:108 0.012
Tags: @product
1:28.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login 51.096
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 24.913
And I take note of which tps features are available 3.797
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 8.018
After features/support/hooks.rb:339 0.241
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.677
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.292
Then Tails is running from USB drive "old" 0.322
And all tps features are active 4.921
When I write some files expected to persist 1.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.926
And I take note of which tps features are available 3.597
And I shutdown Tails and wait for the computer to power off 8.048
# 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.813
After features/support/hooks.rb:339 0.157
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.458
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.129
And I log in to a new session 11.910
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.656
And I plug USB drive "to_upgrade" 2.190
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.146
Then the running Tails is installed on USB drive "to_upgrade" 15.137
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 3.833
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.792
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:3.599
Then all tps features from the old Tails version are active 0.947
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.237
And the expected persistent files created with the old Tails version are present in the filesystem 0.996
And all persistent directories from the old Tails version have safe access rights 1.710
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.429
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.000
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.016
And Tor is ready 12.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.459
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.324
Given I shutdown Tails and wait for the computer to power off 6.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.591
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.745
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.190
When the network is plugged 0.013
And Tor is ready 9.966
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.021
Given I shutdown Tails and wait for the computer to power off 4.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.822
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.713
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.012
And Tor is ready 10.568
Then the Upgrader considers the system as up-to-date 10.486
# 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.781
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.963
After features/support/hooks.rb:108 0.043
Tags: @product @automatic_upgrade
19.552
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.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 8.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.683
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.000