Project Number Date
test_Tails_ISO_21771-test-reliable-celluloid-open 4 08 Sep 2026, 03:43

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:0.262 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:3.351
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.190
When I start Tails from USB drive "old" with network unplugged 46.288
Then the boot device has safe access rights 2.203
And Tails is running from USB drive "old" 0.192
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.137
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 1.383
After features/support/hooks.rb:108 0.006
Tags: @product
1:20.543
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 46.954
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 22.116
And I take note of which tps features are available 5.630
Then a Tails persistence partition exists on USB drive "old" 0.423
And I shutdown Tails and wait for the computer to power off 5.098
After features/support/hooks.rb:339 0.307
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.113
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.595
Then Tails is running from USB drive "old" 0.225
And all tps features are active 6.951
When I write some files expected to persist 1.028
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.256
And all persistent directories from the old Tails version have safe access rights 1.499
And I take note of which tps features are available 5.694
And I shutdown Tails and wait for the computer to power off 2.520
# 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.133
After features/support/hooks.rb:339 0.155
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.751
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.204
And I log in to a new session 12.372
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.607
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.600
Then the running Tails is installed on USB drive "to_upgrade" 17.512
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 0.541
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.231
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.334
Then all tps features from the old Tails version are active 1.170
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 1.977
And the expected persistent files created with the old Tails version are present in the filesystem 0.935
And all persistent directories from the old Tails version have safe access rights 1.493
After features/support/hooks.rb:339 0.873
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:34.401
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 20.763
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
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.176
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.246
When the network is plugged 0.033
And Tor is ready 13.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.901
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.200
Given I shutdown Tails and wait for the computer to power off 5.440
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.724
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.748
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.164
When the network is plugged 0.027
And Tor is ready 10.009
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.492
Given I shutdown Tails and wait for the computer to power off 4.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.234
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.225
And the file system changes introduced in version 6.3~testoverlayfs are present 0.340
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.080
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.148
When the network is plugged 0.025
And Tor is ready 10.142
Then the Upgrader considers the system as up-to-date 0.113
# 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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.265
After features/support/hooks.rb:339 0.933
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.870
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.614
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
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.029
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.029
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.933
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.000