Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 2 16 Jun 2025, 20:34

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:34.967 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.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 38.541
When I start Tails from USB drive "old" with network unplugged 1:34.358
Then the boot device has safe access rights 4.822
And Tails is running from USB drive "old" 0.437
And there is no persistence partition on USB drive "old" 0.117
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.429
And I unplug USB drive "old" 0.264
After features/support/hooks.rb:330 3.593
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.765
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:38.642
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 37.925
And I take note of which tps features are available 2.829
Then a Tails persistence partition exists on USB drive "old" 0.901
And I shutdown Tails and wait for the computer to power off 10.944
After features/support/hooks.rb:330 0.223
After features/support/hooks.rb:100 0.009
Tags: @product
3:29.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.305
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:41.553
Then Tails is running from USB drive "old" 1.342
And all tps features are active 2.581
When I write some files expected to persist 2.097
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.733
And I take note of which tps features are available 0.649
And I shutdown Tails and wait for the computer to power off 7.739
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.946
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.007
Tags: @product
2:52.123
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 without a persistent partition and stopped at Tails Greeter's login screen 10.958
And I log in to a new session 20.676
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.065
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.800
Then the running Tails is installed on USB drive "to_upgrade" 30.405
And I unplug USB drive "to_upgrade" 0.272
And I unplug USB drive "__internal" 0.386
After features/support/hooks.rb:330 4.251
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.562
Then all tps features from the old Tails version are active 1.886
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.650
And the expected persistent files created with the old Tails version are present in the filesystem 1.665
And all persistent directories from the old Tails version have safe access rights 3.845
After features/support/hooks.rb:330 1.765
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:9.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.728
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.547
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.525
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.570
When the network is plugged 0.096
And Tor is ready 24.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.740
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.906
Given I shutdown Tails and wait for the computer to power off 11.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.888
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.093
And the file system changes introduced in version 6.2~testoverlayfs are present 0.470
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# 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.300
When the network is plugged 0.068
And Tor is ready 19.986
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.136
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.406
Given I shutdown Tails and wait for the computer to power off 4.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.955
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.331
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.072
And Tor is ready 19.687
Then the Upgrader considers the system as up-to-date 0.331
# 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.256
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.454
After features/support/hooks.rb:330 0.707
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.879
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 10.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.619
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.214
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 21.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.299
After features/support/hooks.rb:330 0.815
After features/support/hooks.rb:100 0.000