Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 11 09 Aug 2026, 23:20

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:21.874 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.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.295
When I start Tails from USB drive "old" with network unplugged 1:0.055
Then the boot device has safe access rights 1.947
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 1.453
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.064
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 50.375
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 22.992
And I take note of which tps features are available 5.778
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 4.055
After features/support/hooks.rb:339 0.303
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.490
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.060
Then Tails is running from USB drive "old" 0.253
And all tps features are active 7.206
When I write some files expected to persist 0.989
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.234
And all persistent directories from the old Tails version have safe access rights 1.515
And I take note of which tps features are available 6.131
And I shutdown Tails and wait for the computer to power off 4.030
# 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.851
After features/support/hooks.rb:339 0.322
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.717
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.650
And I log in to a new session 11.290
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.962
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.956
Then the running Tails is installed on USB drive "to_upgrade" 18.398
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.708
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.431
Then all tps features from the old Tails version are active 1.141
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 2.553
And the expected persistent files created with the old Tails version are present in the filesystem 1.070
And all persistent directories from the old Tails version have safe access rights 2.239
After features/support/hooks.rb:339 0.479
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
3:52.718
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.584
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.037
And Tor is ready 13.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.703
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.574
Given I shutdown Tails and wait for the computer to power off 5.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.518
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.163
When the network is plugged 0.024
And Tor is ready 10.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.989
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.770
Given I shutdown Tails and wait for the computer to power off 2.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.618
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.667
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.030
And Tor is ready 10.127
Then the Upgrader considers the system as up-to-date 10.461
# 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.134
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
47.176
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 35.566
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
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.056
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.608
After features/support/hooks.rb:339 0.572
After features/support/hooks.rb:108 0.000