Project Number Date
test_Tails_ISO_21582-stable-flatpak-project-on-jenkins 1 03 Sep 2026, 20:15

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:59.026 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:22.506
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.399
When I start Tails from USB drive "old" with network unplugged 1:4.358
Then the boot device has safe access rights 2.065
And Tails is running from USB drive "old" 0.179
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.400
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.386
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 48.850
Then Tails is running from USB drive "old" 0.182
And I create a persistent partition 23.302
And I take note of which tps features are available 7.411
Then a Tails persistence partition exists on USB drive "old" 0.471
And I shutdown Tails and wait for the computer to power off 4.050
After features/support/hooks.rb:339 0.472
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.592
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.080
Then Tails is running from USB drive "old" 0.208
And all tps features are active 9.456
When I write some files expected to persist 1.195
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.144
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.600
And I take note of which tps features are available 6.650
And I shutdown Tails and wait for the computer to power off 2.714
# 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.116
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.988
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.617
And I log in to a new session 12.458
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.801
Then the running Tails is installed on USB drive "to_upgrade" 18.751
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 1.700
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.775
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.178
Then all tps features from the old Tails version are active 1.353
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.556
And the expected persistent files created with the old Tails version are present in the filesystem 1.181
And all persistent directories from the old Tails version have safe access rights 2.154
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:50.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.444
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.034
And Tor is ready 12.320
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.082
Given I shutdown Tails and wait for the computer to power off 5.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.711
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.117
# 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.268
When the network is plugged 0.024
And Tor is ready 10.673
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.917
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.821
Given I shutdown Tails and wait for the computer to power off 4.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.866
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.774
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.032
And Tor is ready 13.208
Then the Upgrader considers the system as up-to-date 10.496
# 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.162
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.297
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.278
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.983
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.000