Project Number Date
test_Tails_ISO_21769-gather-chutney-configure-backtrace 2 08 Sep 2026, 16:04

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:5.266 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:21.499
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.119
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 14.392
When I start Tails from USB drive "old" with network unplugged 1:2.756
Then the boot device has safe access rights 2.602
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.178
After features/support/hooks.rb:108 0.007
Tags: @product
1:23.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 49.461
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 24.271
And I take note of which tps features are available 6.743
Then a Tails persistence partition exists on USB drive "old" 0.570
And I shutdown Tails and wait for the computer to power off 2.613
After features/support/hooks.rb:339 0.369
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.575
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.655
Then Tails is running from USB drive "old" 0.307
And all tps features are active 8.436
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.726
And I take note of which tps features are available 7.396
And I shutdown Tails and wait for the computer to power off 4.166
# 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.949
After features/support/hooks.rb:339 0.334
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.800
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 9.216
And I log in to a new session 13.060
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.845
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.504
Then the running Tails is installed on USB drive "to_upgrade" 19.645
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:339 2.017
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.137
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.798
Then all tps features from the old Tails version are active 1.392
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.208
And the expected persistent files created with the old Tails version are present in the filesystem 1.264
And all persistent directories from the old Tails version have safe access rights 1.697
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:45.880
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 8.274
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.026
And Tor is ready 11.794
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.752
Given I shutdown Tails and wait for the computer to power off 5.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.956
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# 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.197
When the network is plugged 0.028
And Tor is ready 10.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.794
Given I shutdown Tails and wait for the computer to power off 2.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.261
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.336
And the file system changes introduced in version 6.3~testoverlayfs are present 0.427
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.040
And Tor is ready 10.563
Then the Upgrader considers the system as up-to-date 0.175
# 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.525
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 1.359
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
21.813
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.904
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
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.046
And Tor is ready 10.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.361
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.000