Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 34 03 Apr 2025, 22:23

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 18:44.026 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:1.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.591
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.543
When I start Tails from USB drive "old" with network unplugged 1:25.729
Then the boot device has safe access rights 3.201
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 6.832
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:22.408
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 31.768
And I take note of which tps features are available 1.902
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.256
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.852
Then Tails is running from USB drive "old" 0.330
And all tps features are active 2.042
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.314
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 6.178
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.121
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.049
Tags: @product
2:31.231
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 without a persistent partition and stopped at Tails Greeter's login screen 9.849
And I log in to a new session 18.955
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.378
And I plug USB drive "to_upgrade" 2.407
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.466
Then the running Tails is installed on USB drive "to_upgrade" 25.747
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 1.055
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.343
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.645
Then all tps features from the old Tails version are active 1.607
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.561
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:330 1.496
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:18.175
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.772
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.071
And Tor is ready 22.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.813
Given I shutdown Tails and wait for the computer to power off 8.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.896
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.277
When the network is plugged 0.078
And Tor is ready 16.711
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.235
Given I shutdown Tails and wait for the computer to power off 4.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.296
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.934
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.083
And Tor is ready 19.666
Then the Upgrader considers the system as up-to-date 0.325
# 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 16.053
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.950
After features/support/hooks.rb:330 0.724
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.746
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 9.471
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
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.116
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 20.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.885
After features/support/hooks.rb:330 0.639
After features/support/hooks.rb:100 0.000