Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 16 01 Jul 2025, 21:06

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.112 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:1.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 41.509
When I start Tails from USB drive "old" with network unplugged 2:13.473
Then the boot device has safe access rights 3.793
And Tails is running from USB drive "old" 0.422
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.143
And udev-watchdog is monitoring the correct device 0.376
And I unplug USB drive "old" 0.347
After features/support/hooks.rb:330 10.220
After features/support/hooks.rb:100 0.078
Tags: @product
2:52.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.052
Given a computer 0.534
And I start Tails from USB drive "old" with network unplugged and I login 1:56.870
Then Tails is running from USB drive "old" 1.543
And I create a persistent partition 40.877
And I take note of which tps features are available 2.928
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.593
After features/support/hooks.rb:330 1.293
After features/support/hooks.rb:100 0.409
Tags: @product
4:9.088
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.184
Given a computer 0.655
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:8.424
Then Tails is running from USB drive "old" 0.865
And all tps features are active 2.127
When I write some files expected to persist 1.991
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.573
And all persistent directories from the old Tails version have safe access rights 5.344
And I take note of which tps features are available 1.265
And I shutdown Tails and wait for the computer to power off 8.601
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.975
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.874
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 without a persistent partition and stopped at Tails Greeter's login screen 10.967
And I log in to a new session 30.732
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.497
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.212
Then the running Tails is installed on USB drive "to_upgrade" 41.327
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.298
After features/support/hooks.rb:330 2.766
After features/support/hooks.rb:100 0.000
Tags: @product
3:23.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.261
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:5.422
Then all tps features from the old Tails version are active 2.132
And Tails is running from USB drive "to_upgrade" 2.414
And the boot device has safe access rights 8.458
And the expected persistent files created with the old Tails version are present in the filesystem 1.681
And all persistent directories from the old Tails version have safe access rights 3.004
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
9:46.472
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.458
And no SquashFS delta is installed 0.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.834
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.736
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.591
When the network is plugged 0.082
And Tor is ready 32.097
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.207
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.781
Given I shutdown Tails and wait for the computer to power off 20.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:59.568
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.457
And the file system changes introduced in version 6.2~testoverlayfs are present 3.536
And only the 6.2~testoverlayfs SquashFS delta is installed 0.668
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.695
# 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.867
When the network is plugged 0.103
And Tor is ready 24.228
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.102
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.158
Given I shutdown Tails and wait for the computer to power off 9.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.868
Then Tails is running version 6.3~testoverlayfs 0.127
And all tps features are active 5.671
And the file system changes introduced in version 6.3~testoverlayfs are present 1.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.192
# 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.567
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.506
When the network is plugged 0.149
And Tor is ready 25.610
Then the Upgrader considers the system as up-to-date 0.364
# 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 23.572
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 4.864
After features/support/hooks.rb:330 2.001
After features/support/hooks.rb:100 0.096
Tags: @product @automatic_upgrade
46.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 27.224
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.575
After features/support/hooks.rb:330 1.711
After features/support/hooks.rb:100 0.000