Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 12 27 Jun 2025, 21:31

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 27:17.946 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
3:0.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given a computer 0.476
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 40.781
When I start Tails from USB drive "old" with network unplugged 2:9.516
Then the boot device has safe access rights 7.906
And Tails is running from USB drive "old" 0.422
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:330 15.534
After features/support/hooks.rb:100 0.025
Tags: @product
3:1.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 2:1.012
Then Tails is running from USB drive "old" 1.453
And I create a persistent partition 43.738
And I take note of which tps features are available 2.582
Then a Tails persistence partition exists on USB drive "old" 0.941
And I shutdown Tails and wait for the computer to power off 12.004
After features/support/hooks.rb:330 0.293
After features/support/hooks.rb:100 0.072
Tags: @product
4:33.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.519
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:23.861
Then Tails is running from USB drive "old" 1.963
And all tps features are active 3.328
When I write some files expected to persist 8.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.439
And all persistence configuration files have safe access rights 0.799
And all persistent directories from the old Tails version have safe access rights 4.046
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 6.503
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 42.685
After features/support/hooks.rb:330 0.987
After features/support/hooks.rb:100 0.028
Tags: @product
3:24.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.933
And I log in to a new session 33.099
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.585
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.010
Then the running Tails is installed on USB drive "to_upgrade" 42.390
And I unplug USB drive "to_upgrade" 1.093
And I unplug USB drive "__internal" 0.311
After features/support/hooks.rb:330 4.916
After features/support/hooks.rb:100 0.000
Tags: @product
3:18.825
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.324
Then all tps features from the old Tails version are active 1.930
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 9.975
And the expected persistent files created with the old Tails version are present in the filesystem 3.104
And all persistent directories from the old Tails version have safe access rights 2.936
After features/support/hooks.rb:330 1.284
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:58.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.532
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.697
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.084
And Tor is ready 29.631
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.966
Given I shutdown Tails and wait for the computer to power off 9.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.558
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.662
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.116
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.298
When the network is plugged 0.075
And Tor is ready 26.372
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.806
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.914
Given I shutdown Tails and wait for the computer to power off 6.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:36.046
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.643
And the file system changes introduced in version 6.3~testoverlayfs are present 0.677
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.083
And Tor is ready 30.378
Then the Upgrader considers the system as up-to-date 0.641
# 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 25.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.700
After features/support/hooks.rb:330 0.785
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
59.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.954
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.144
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 33.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.792
After features/support/hooks.rb:330 1.214
After features/support/hooks.rb:100 0.000