Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 33 02 Apr 2025, 22:15

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 21:43.027 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:20.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 38.276
When I start Tails from USB drive "old" with network unplugged 1:36.298
Then the boot device has safe access rights 3.407
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.132
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:330 7.043
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.511
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:32.689
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.450
And I take note of which tps features are available 1.776
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.257
After features/support/hooks.rb:330 0.236
After features/support/hooks.rb:100 0.009
Tags: @product
3:9.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.495
Then Tails is running from USB drive "old" 1.777
And all tps features are active 2.491
When I write some files expected to persist 3.304
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.616
And I take note of which tps features are available 0.603
And I shutdown Tails and wait for the computer to power off 6.590
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.582
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.793
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.771
And I log in to a new session 21.186
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.044
And I plug USB drive "to_upgrade" 2.543
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.479
Then the running Tails is installed on USB drive "to_upgrade" 29.222
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.323
After features/support/hooks.rb:330 2.659
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.282
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.408
And the expected persistent files created with the old Tails version are present in the filesystem 1.579
And all persistent directories from the old Tails version have safe access rights 3.116
After features/support/hooks.rb:330 1.705
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:37.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.579
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.574
When the network is plugged 0.092
And Tor is ready 20.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.721
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.212
Given I shutdown Tails and wait for the computer to power off 12.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.310
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.867
And the file system changes introduced in version 6.2~testoverlayfs are present 0.506
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.450
# 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.818
When the network is plugged 0.086
And Tor is ready 23.196
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.228
Given I shutdown Tails and wait for the computer to power off 7.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.421
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.324
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.082
And Tor is ready 23.637
Then the Upgrader considers the system as up-to-date 0.421
# 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 17.002
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.594
After features/support/hooks.rb:330 0.733
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.755
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.526
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 22.475
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.358
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.000