Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 30 16 Jun 2026, 20:14

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:31.014 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:24.817
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.452
When I start Tails from USB drive "old" with network unplugged 1:6.359
Then the boot device has safe access rights 2.959
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 4.071
After features/support/hooks.rb:108 0.023
Tags: @product
1:32.612
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 55.914
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 25.965
And I take note of which tps features are available 4.575
Then a Tails persistence partition exists on USB drive "old" 0.580
And I shutdown Tails and wait for the computer to power off 5.125
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.023
Tags: @product
1:42.909
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.040
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.441
Then Tails is running from USB drive "old" 0.282
And all tps features are active 5.832
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.336
And all persistent directories from the old Tails version have safe access rights 2.130
And I take note of which tps features are available 4.615
And I shutdown Tails and wait for the computer to power off 4.583
# 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" 13.461
After features/support/hooks.rb:339 0.458
After features/support/hooks.rb:108 0.022
Tags: @product
2:13.933
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.341
And I log in to a new session 14.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.727
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.175
Then the running Tails is installed on USB drive "to_upgrade" 15.850
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.915
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.992
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.858
Then all tps features from the old Tails version are active 0.955
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.463
And the expected persistent files created with the old Tails version are present in the filesystem 1.222
And all persistent directories from the old Tails version have safe access rights 2.081
After features/support/hooks.rb:339 0.807
After features/support/hooks.rb:108 0.053
Tags: @product @automatic_upgrade
4:0.697
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.055
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.016
And Tor is ready 13.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.583
Given I shutdown Tails and wait for the computer to power off 6.952
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.378
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.761
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.217
When the network is plugged 0.014
And Tor is ready 10.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.997
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.970
Given I shutdown Tails and wait for the computer to power off 4.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.716
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.960
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.015
And Tor is ready 12.250
Then the Upgrader considers the system as up-to-date 10.590
# 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.448
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.042
Tags: @product @automatic_upgrade
20.050
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
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.067
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.134
After features/support/hooks.rb:339 0.678
After features/support/hooks.rb:108 0.000