Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 60 12 Jun 2026, 14:30

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:15.148 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:13.234
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.851
When I start Tails from USB drive "old" with network unplugged 54.155
Then the boot device has safe access rights 3.159
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 1.577
After features/support/hooks.rb:108 0.028
Tags: @product
1:30.764
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 55.601
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.494
And I take note of which tps features are available 4.043
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 4.579
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.016
Tags: @product
1:38.535
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.363
Then Tails is running from USB drive "old" 0.356
And all tps features are active 5.130
When I write some files expected to persist 1.501
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.132
And I take note of which tps features are available 4.465
And I shutdown Tails and wait for the computer to power off 4.209
# 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.659
After features/support/hooks.rb:339 0.291
After features/support/hooks.rb:108 0.018
Tags: @product
2:11.041
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.015
And I log in to a new session 12.335
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.923
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.916
Then the running Tails is installed on USB drive "to_upgrade" 15.318
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 2.179
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.033
Given a computer 0.131
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.537
Then all tps features from the old Tails version are active 1.113
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.727
And the expected persistent files created with the old Tails version are present in the filesystem 1.323
And all persistent directories from the old Tails version have safe access rights 2.075
After features/support/hooks.rb:339 0.627
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:3.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.298
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.016
And Tor is ready 13.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.810
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.655
Given I shutdown Tails and wait for the computer to power off 9.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.237
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.232
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.225
When the network is plugged 0.013
And Tor is ready 9.709
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.790
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.142
Given I shutdown Tails and wait for the computer to power off 8.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.451
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.528
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.014
And Tor is ready 10.028
Then the Upgrader considers the system as up-to-date 10.617
# 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.841
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:339 1.019
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
21.465
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.736
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.027
And Tor is ready 10.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.922
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.000