Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 9 24 Jun 2025, 22:29

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 28:38.597 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:48.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 41.709
When I start Tails from USB drive "old" with network unplugged 1:59.805
Then the boot device has safe access rights 4.571
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 6.326
After features/support/hooks.rb:100 0.028
Tags: @product
3:7.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.581
And I start Tails from USB drive "old" with network unplugged and I login 1:58.465
Then Tails is running from USB drive "old" 3.299
And I create a persistent partition 48.075
And I take note of which tps features are available 2.831
Then a Tails persistence partition exists on USB drive "old" 3.741
And I shutdown Tails and wait for the computer to power off 10.258
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
4:58.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:46.337
Then Tails is running from USB drive "old" 2.783
And all tps features are active 6.001
When I write some files expected to persist 2.599
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 3.030
And I take note of which tps features are available 0.916
And I shutdown Tails and wait for the computer to power off 11.321
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 44.520
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.010
Tags: @product
3:41.587
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 15.577
And I log in to a new session 30.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.288
And I plug USB drive "to_upgrade" 9.324
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:2.707
Then the running Tails is installed on USB drive "to_upgrade" 40.829
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 4.834
After features/support/hooks.rb:100 0.000
Tags: @product
3:31.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.056
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:13.987
Then all tps features from the old Tails version are active 1.865
And Tails is running from USB drive "to_upgrade" 0.549
And the boot device has safe access rights 4.033
And the expected persistent files created with the old Tails version are present in the filesystem 6.349
And all persistent directories from the old Tails version have safe access rights 4.830
After features/support/hooks.rb:330 0.963
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
9:36.544
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 15.547
And no SquashFS delta is installed 0.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.808
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.192
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.632
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.879
When the network is plugged 0.092
And Tor is ready 34.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.631
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.889
Given I shutdown Tails and wait for the computer to power off 12.710
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:56.445
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 5.967
And the file system changes introduced in version 6.2~testoverlayfs are present 1.468
And only the 6.2~testoverlayfs SquashFS delta is installed 0.351
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.501
# 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.635
When the network is plugged 0.073
And Tor is ready 25.021
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 15.422
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.386
Given I shutdown Tails and wait for the computer to power off 9.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:3.086
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.479
And the file system changes introduced in version 6.3~testoverlayfs are present 0.657
And only the 6.3~testoverlayfs SquashFS delta is installed 0.131
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.392
When the network is plugged 0.131
And Tor is ready 22.819
Then the Upgrader considers the system as up-to-date 0.300
# 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 26.627
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.642
After features/support/hooks.rb:330 1.024
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
54.364
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.377
And the signing key used by the Upgrader is outdated 0.409
But a current signing key is available on our website 0.000
When the network is plugged 0.158
And Tor is ready 30.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.741
After features/support/hooks.rb:330 3.366
After features/support/hooks.rb:100 0.000