Project Number Date
test_Tails_ISO_21615-debian-security-updates-supersede-custom-packages 2 26 May 2026, 01:45

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 11:20.422 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
1:17.530
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.818
When I start Tails from USB drive "old" with network unplugged 1:0.194
Then the boot device has safe access rights 2.754
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:335 1.484
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.875
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.643
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 24.187
And I take note of which tps features are available 0.377
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 7.871
After features/support/hooks.rb:335 0.512
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.253
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.697
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.001
When I write some files expected to persist 1.197
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.746
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 8.248
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.479
After features/support/hooks.rb:335 0.589
After features/support/hooks.rb:104 0.006
Tags: @product
2:10.596
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.548
And I log in to a new session 12.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.175
Then the running Tails is installed on USB drive "to_upgrade" 15.149
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:335 3.634
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.603
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.124
Then all tps features from the old Tails version are active 0.967
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.431
And the expected persistent files created with the old Tails version are present in the filesystem 1.062
And all persistent directories from the old Tails version have safe access rights 1.735
After features/support/hooks.rb:335 0.604
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:38.627
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.125
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.037
And Tor is ready 14.642
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.163
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.609
Given I shutdown Tails and wait for the computer to power off 10.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.024
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.209
When the network is plugged 0.018
And Tor is ready 11.288
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.281
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.683
Given I shutdown Tails and wait for the computer to power off 8.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.356
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.013
And Tor is ready 10.748
Then the Upgrader considers the system as up-to-date 10.540
# 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 3.755
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:335 0.850
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.935
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.280
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.285
After features/support/hooks.rb:335 0.856
After features/support/hooks.rb:104 0.000