Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 3 17 Jun 2025, 23:50

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:43.748 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.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 41.898
When I start Tails from USB drive "old" with network unplugged 2:13.557
Then the boot device has safe access rights 3.161
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.567
After features/support/hooks.rb:330 6.217
After features/support/hooks.rb:100 0.087
Tags: @product
3:8.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.063
Given a computer 0.803
And I start Tails from USB drive "old" with network unplugged and I login 2:5.333
Then Tails is running from USB drive "old" 0.994
And I create a persistent partition 46.635
And I take note of which tps features are available 2.673
Then a Tails persistence partition exists on USB drive "old" 1.893
And I shutdown Tails and wait for the computer to power off 10.388
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
4:16.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:12.202
Then Tails is running from USB drive "old" 3.185
And all tps features are active 3.399
When I write some files expected to persist 2.013
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.960
And I take note of which tps features are available 0.638
And I shutdown Tails and wait for the computer to power off 10.714
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.449
After features/support/hooks.rb:330 0.387
After features/support/hooks.rb:100 0.026
Tags: @product
3:41.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 28.581
And I log in to a new session 35.285
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.621
And I plug USB drive "to_upgrade" 2.633
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.208
Then the running Tails is installed on USB drive "to_upgrade" 40.742
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 3.694
After features/support/hooks.rb:100 0.000
Tags: @product
3:24.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:5.843
Then all tps features from the old Tails version are active 6.184
And Tails is running from USB drive "to_upgrade" 0.941
And the boot device has safe access rights 5.959
And the expected persistent files created with the old Tails version are present in the filesystem 1.789
And all persistent directories from the old Tails version have safe access rights 3.616
After features/support/hooks.rb:330 3.518
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
9:15.661
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.391
And no SquashFS delta is installed 0.453
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.508
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.732
And the file system changes introduced in version 6.3~testoverlayfs are not present 2.119
When the network is plugged 0.298
And Tor is ready 23.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.825
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.593
Given I shutdown Tails and wait for the computer to power off 14.818
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:49.522
Then Tails is running version 6.2~testoverlayfs 0.034
And all tps features are active 4.889
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.497
# 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.099
And Tor is ready 25.005
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 14.629
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.471
Given I shutdown Tails and wait for the computer to power off 7.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.344
Then Tails is running version 6.3~testoverlayfs 0.414
And all tps features are active 3.932
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.070
And Tor is ready 22.276
Then the Upgrader considers the system as up-to-date 0.391
# 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 21.326
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.492
After features/support/hooks.rb:330 1.112
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
55.507
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 17.285
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.143
And the signing key used by the Upgrader is outdated 0.185
But a current signing key is available on our website 0.000
When the network is plugged 0.130
And Tor is ready 29.619
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.662
After features/support/hooks.rb:330 1.146
After features/support/hooks.rb:100 0.000