Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 10 25 Jun 2025, 21:51

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 28:28.404 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
2:58.987
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 43.102
When I start Tails from USB drive "old" with network unplugged 2:5.193
Then the boot device has safe access rights 7.855
And Tails is running from USB drive "old" 0.510
And there is no persistence partition on USB drive "old" 0.172
And process "udev-watchdog" is running 0.231
And udev-watchdog is monitoring the correct device 0.424
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.876
After features/support/hooks.rb:100 0.036
Tags: @product
3:5.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login 2:2.234
Then Tails is running from USB drive "old" 0.696
And I create a persistent partition 47.775
And I take note of which tps features are available 4.129
Then a Tails persistence partition exists on USB drive "old" 0.996
And I shutdown Tails and wait for the computer to power off 9.290
After features/support/hooks.rb:330 1.003
After features/support/hooks.rb:100 0.033
Tags: @product
4:24.091
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.741
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:18.501
Then Tails is running from USB drive "old" 2.541
And all tps features are active 4.723
When I write some files expected to persist 2.561
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 10.974
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.232
After features/support/hooks.rb:330 0.440
After features/support/hooks.rb:100 0.041
Tags: @product
3:24.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.432
And I log in to a new session 32.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.431
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.469
Then the running Tails is installed on USB drive "to_upgrade" 42.186
And I unplug USB drive "to_upgrade" 0.365
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 0.955
After features/support/hooks.rb:100 0.000
Tags: @product
3:38.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:17.308
Then all tps features from the old Tails version are active 2.915
And Tails is running from USB drive "to_upgrade" 0.434
And the boot device has safe access rights 4.749
And the expected persistent files created with the old Tails version are present in the filesystem 1.994
And all persistent directories from the old Tails version have safe access rights 11.300
After features/support/hooks.rb:330 5.251
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
9:58.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.052
And no SquashFS delta is installed 0.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.661
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.536
When the network is plugged 1.125
And Tor is ready 31.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.969
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.068
Given I shutdown Tails and wait for the computer to power off 21.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:3.110
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 3.736
And the file system changes introduced in version 6.2~testoverlayfs are present 0.412
And only the 6.2~testoverlayfs SquashFS delta is installed 0.123
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.618
# 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.524
When the network is plugged 0.086
And Tor is ready 24.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.677
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.097
Given I shutdown Tails and wait for the computer to power off 8.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:5.417
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 4.625
And the file system changes introduced in version 6.3~testoverlayfs are present 1.001
And only the 6.3~testoverlayfs SquashFS delta is installed 0.120
# 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.569
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.623
When the network is plugged 0.214
And Tor is ready 23.609
Then the Upgrader considers the system as up-to-date 0.327
# 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 21.909
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.564
After features/support/hooks.rb:330 0.803
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
57.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.131
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 31.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.821
After features/support/hooks.rb:330 0.991
After features/support/hooks.rb:100 0.000