Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 39 26 Jun 2026, 20:11

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 12:10.942 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:10.937
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.488
When I start Tails from USB drive "old" with network unplugged 53.053
Then the boot device has safe access rights 2.594
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.617
After features/support/hooks.rb:108 0.011
Tags: @product
1:34.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 55.733
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 25.207
And I take note of which tps features are available 4.667
Then a Tails persistence partition exists on USB drive "old" 0.587
And I shutdown Tails and wait for the computer to power off 8.387
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.860
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.677
Then Tails is running from USB drive "old" 0.305
And all tps features are active 5.550
When I write some files expected to persist 1.459
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.328
And all persistent directories from the old Tails version have safe access rights 1.864
And I take note of which tps features are available 4.167
And I shutdown Tails and wait for the computer to power off 7.908
# 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.365
After features/support/hooks.rb:339 0.561
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.127
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.137
And I log in to a new session 13.813
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.868
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.198
Then the running Tails is installed on USB drive "to_upgrade" 15.539
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:339 2.443
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.690
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.210
Then all tps features from the old Tails version are active 1.074
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.514
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.216
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:55.515
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.330
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.017
And Tor is ready 13.527
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.200
Given I shutdown Tails and wait for the computer to power off 7.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.659
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.038
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.221
When the network is plugged 0.020
And Tor is ready 11.232
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.790
Given I shutdown Tails and wait for the computer to power off 4.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.965
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.241
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.199
When the network is plugged 0.014
And Tor is ready 11.650
Then the Upgrader considers the system as up-to-date 10.606
# 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.354
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 1.218
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
20.917
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.434
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.805
After features/support/hooks.rb:339 0.880
After features/support/hooks.rb:108 0.000