Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 14 29 Jun 2025, 21:00

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:33.720 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:57.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 39.638
When I start Tails from USB drive "old" with network unplugged 2:4.038
Then the boot device has safe access rights 4.080
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.796
And I unplug USB drive "old" 6.841
After features/support/hooks.rb:330 2.792
After features/support/hooks.rb:100 0.037
Tags: @product
3:11.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.608
And I start Tails from USB drive "old" with network unplugged and I login 2:8.668
Then Tails is running from USB drive "old" 0.498
And I create a persistent partition 47.699
And I take note of which tps features are available 3.259
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 9.422
After features/support/hooks.rb:330 1.302
After features/support/hooks.rb:100 0.072
Tags: @product
4:22.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given a computer 0.765
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:24.351
Then Tails is running from USB drive "old" 1.224
And all tps features are active 2.785
When I write some files expected to persist 1.773
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 3.465
And I take note of which tps features are available 0.556
And I shutdown Tails and wait for the computer to power off 9.652
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.465
After features/support/hooks.rb:330 0.263
After features/support/hooks.rb:100 0.031
Tags: @product
3:22.775
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 13.045
And I log in to a new session 33.209
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.534
And I plug USB drive "to_upgrade" 2.645
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.680
Then the running Tails is installed on USB drive "to_upgrade" 41.064
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.358
After features/support/hooks.rb:330 2.426
After features/support/hooks.rb:100 0.000
Tags: @product
3:19.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:1.518
Then all tps features from the old Tails version are active 1.903
And Tails is running from USB drive "to_upgrade" 0.507
And the boot device has safe access rights 4.189
And the expected persistent files created with the old Tails version are present in the filesystem 5.746
And all persistent directories from the old Tails version have safe access rights 5.920
After features/support/hooks.rb:330 1.312
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
9:18.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.549
And no SquashFS delta is installed 0.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.483
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.516
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.908
When the network is plugged 0.253
And Tor is ready 25.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.218
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.742
Given I shutdown Tails and wait for the computer to power off 11.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:1.598
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 5.896
And the file system changes introduced in version 6.2~testoverlayfs are present 0.913
And only the 6.2~testoverlayfs SquashFS delta is installed 0.285
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.693
# 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.744
When the network is plugged 0.610
And Tor is ready 22.946
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.599
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.563
Given I shutdown Tails and wait for the computer to power off 5.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:55.967
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.955
And the file system changes introduced in version 6.3~testoverlayfs are present 0.642
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.532
When the network is plugged 0.422
And Tor is ready 24.228
Then the Upgrader considers the system as up-to-date 0.534
# 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 23.716
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.313
After features/support/hooks.rb:330 0.768
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:1.085
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 26.673
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 28.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.322
After features/support/hooks.rb:330 1.284
After features/support/hooks.rb:100 0.000