Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 13 28 Jun 2025, 21:16

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 27:40.129 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
3:1.877
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 40.870
When I start Tails from USB drive "old" with network unplugged 2:14.463
Then the boot device has safe access rights 4.218
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 10.188
After features/support/hooks.rb:100 0.025
Tags: @product
3:4.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.512
And I start Tails from USB drive "old" with network unplugged and I login 2:1.204
Then Tails is running from USB drive "old" 3.078
And I create a persistent partition 43.930
And I take note of which tps features are available 2.707
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 12.519
After features/support/hooks.rb:330 0.407
After features/support/hooks.rb:100 0.009
Tags: @product
4:7.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:8.329
Then Tails is running from USB drive "old" 0.576
And all tps features are active 2.593
When I write some files expected to persist 9.794
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.400
And all persistence configuration files have safe access rights 0.782
And all persistent directories from the old Tails version have safe access rights 2.601
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 6.606
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.416
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
3:30.707
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 without a persistent partition and stopped at Tails Greeter's login screen 17.452
And I log in to a new session 25.743
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.684
And I plug USB drive "to_upgrade" 3.702
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.632
Then the running Tails is installed on USB drive "to_upgrade" 39.212
And I unplug USB drive "to_upgrade" 2.886
And I unplug USB drive "__internal" 0.393
After features/support/hooks.rb:330 3.249
After features/support/hooks.rb:100 0.000
Tags: @product
3:21.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.352
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:3.797
Then all tps features from the old Tails version are active 1.897
And Tails is running from USB drive "to_upgrade" 0.570
And the boot device has safe access rights 8.713
And the expected persistent files created with the old Tails version are present in the filesystem 3.189
And all persistent directories from the old Tails version have safe access rights 3.070
After features/support/hooks.rb:330 1.186
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:39.479
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 35.191
And no SquashFS delta is installed 0.459
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.075
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.141
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.411
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.548
When the network is plugged 0.077
And Tor is ready 28.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.235
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.831
Given I shutdown Tails and wait for the computer to power off 12.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:8.101
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.432
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.414
# 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.560
When the network is plugged 0.113
And Tor is ready 29.883
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.030
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.745
Given I shutdown Tails and wait for the computer to power off 7.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.547
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.007
And the file system changes introduced in version 6.3~testoverlayfs are present 0.703
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.507
When the network is plugged 0.098
And Tor is ready 29.284
Then the Upgrader considers the system as up-to-date 0.515
# 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 22.326
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.870
After features/support/hooks.rb:330 0.916
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
53.873
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 13.540
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.158
And the signing key used by the Upgrader is outdated 0.201
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 25.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.019
After features/support/hooks.rb:330 1.300
After features/support/hooks.rb:100 0.000