Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 26 26 Mar 2025, 22: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 19:6.488 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:57.541
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.107
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.927
When I start Tails from USB drive "old" with network unplugged 1:21.160
Then the boot device has safe access rights 3.148
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 6.782
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.746
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:25.280
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 34.066
And I take note of which tps features are available 1.526
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.456
After features/support/hooks.rb:330 0.220
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.672
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.104
When I write some files expected to persist 1.980
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.584
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 6.280
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.465
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.023
Tags: @product
2:32.529
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 without a persistent partition and stopped at Tails Greeter's login screen 10.637
And I log in to a new session 19.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.827
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.485
Then the running Tails is installed on USB drive "to_upgrade" 24.479
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 6.550
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.942
Then all tps features from the old Tails version are active 2.256
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.675
And the expected persistent files created with the old Tails version are present in the filesystem 1.537
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:330 1.581
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:29.969
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 11.369
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.079
And Tor is ready 20.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.274
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.579
Given I shutdown Tails and wait for the computer to power off 8.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.605
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.230
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.072
And Tor is ready 20.693
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.790
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.092
Given I shutdown Tails and wait for the computer to power off 4.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.211
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.059
And Tor is ready 20.979
Then the Upgrader considers the system as up-to-date 0.318
# 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 15.557
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.423
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.369
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 9.978
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 18.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.758
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.000