Project Number Date
test_Tails_ISO_21636-yelp-from-debian 2 02 Jun 2026, 17:48

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:51.267 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:25.322
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.544
When I start Tails from USB drive "old" with network unplugged 1:7.282
Then the boot device has safe access rights 2.703
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:335 1.574
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.435
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 55.979
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 26.736
And I take note of which tps features are available 0.344
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 8.465
After features/support/hooks.rb:335 0.577
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.573
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.284
Then Tails is running from USB drive "old" 0.232
And all tps features are active 1.156
When I write some files expected to persist 1.319
# 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.314
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 8.378
# 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" 12.397
After features/support/hooks.rb:335 0.261
After features/support/hooks.rb:104 0.008
Tags: @product
2:14.017
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.263
And I log in to a new session 13.551
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.816
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.968
Then the running Tails is installed on USB drive "to_upgrade" 15.858
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:335 3.670
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.491
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.996
Then all tps features from the old Tails version are active 0.978
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.776
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 1.977
After features/support/hooks.rb:335 0.803
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:38.702
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.327
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.026
And Tor is ready 12.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.235
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.282
Given I shutdown Tails and wait for the computer to power off 10.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.068
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.016
And Tor is ready 9.971
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.342
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.072
Given I shutdown Tails and wait for the computer to power off 8.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.908
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.232
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.015
And Tor is ready 12.358
Then the Upgrader considers the system as up-to-date 0.106
# 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 4.376
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.420
After features/support/hooks.rb:335 0.866
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.723
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.643
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.811
After features/support/hooks.rb:335 1.077
After features/support/hooks.rb:104 0.000