Project Number Date
test_Tails_ISO_21756-better-support-build-machine 1 30 Sep 2026, 19:11

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 12:18.208 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:24.766
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
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.288
When I start Tails from USB drive "old" with network unplugged 1:6.053
Then the boot device has safe access rights 2.605
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 1.242
After features/support/hooks.rb:108 0.036
Tags: @product
1:30.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 53.320
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.320
And I take note of which tps features are available 7.128
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 3.905
After features/support/hooks.rb:339 0.214
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.384
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.475
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.435
When I write some files expected to persist 1.333
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.318
And all persistent directories from the old Tails version have safe access rights 1.960
And I take note of which tps features are available 6.163
And I shutdown Tails and wait for the computer to power off 2.791
# 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.408
After features/support/hooks.rb:339 0.433
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.774
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 without a persistent partition and stopped at Tails Greeter's login screen 8.697
And I log in to a new session 12.477
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.749
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.007
Then the running Tails is installed on USB drive "to_upgrade" 19.353
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 2.042
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.427
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.318
Then all tps features from the old Tails version are active 1.324
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.165
And all persistent directories from the old Tails version have safe access rights 2.640
After features/support/hooks.rb:339 1.068
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:54.278
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 22.490
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.027
And Tor is ready 13.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.335
Given I shutdown Tails and wait for the computer to power off 5.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.123
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.735
And the file system changes introduced in version 6.2~testoverlayfs are present 0.184
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.258
When the network is plugged 0.047
And Tor is ready 10.593
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.461
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.151
Given I shutdown Tails and wait for the computer to power off 4.106
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.822
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.845
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.199
When the network is plugged 0.036
And Tor is ready 10.354
Then the Upgrader considers the system as up-to-date 0.090
# 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.553
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:339 0.647
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.936
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.471
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.306
After features/support/hooks.rb:339 0.755
After features/support/hooks.rb:108 0.000