Project Number Date
test_Tails_ISO_21761-reduce-chutney-memory-usage 1 11 Sep 2026, 17:03

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 10:58.393 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:3.367
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.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.372
When I start Tails from USB drive "old" with network unplugged 46.561
Then the boot device has safe access rights 1.783
And Tails is running from USB drive "old" 0.159
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.133
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.628
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.228
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 47.664
Then Tails is running from USB drive "old" 0.178
And I create a persistent partition 23.112
And I take note of which tps features are available 6.166
Then a Tails persistence partition exists on USB drive "old" 0.465
And I shutdown Tails and wait for the computer to power off 2.558
After features/support/hooks.rb:339 0.630
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.038
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.696
Then Tails is running from USB drive "old" 0.224
And all tps features are active 7.033
When I write some files expected to persist 1.057
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.203
And all persistent directories from the old Tails version have safe access rights 1.639
And I take note of which tps features are available 5.899
And I shutdown Tails and wait for the computer to power off 5.004
# 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.038
After features/support/hooks.rb:339 0.304
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.180
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.426
And I log in to a new session 10.729
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.192
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.498
Then the running Tails is installed on USB drive "to_upgrade" 17.472
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.126
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.416
Then all tps features from the old Tails version are active 0.940
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 1.986
And the expected persistent files created with the old Tails version are present in the filesystem 0.814
And all persistent directories from the old Tails version have safe access rights 1.675
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.039
3:30.824
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 7.999
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.319
When the network is plugged 0.053
And Tor is ready 13.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.913
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.669
Given I shutdown Tails and wait for the computer to power off 5.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.098
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.160
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.161
When the network is plugged 0.025
And Tor is ready 10.003
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.904
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.601
Given I shutdown Tails and wait for the computer to power off 2.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.769
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.427
And the file system changes introduced in version 6.3~testoverlayfs are present 0.261
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.143
When the network is plugged 0.035
And Tor is ready 10.058
Then the Upgrader considers the system as up-to-date 10.400
# 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 2.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 0.937
After features/support/hooks.rb:108 0.045
18.627
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 7.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 8.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.461
After features/support/hooks.rb:339 0.512
After features/support/hooks.rb:108 0.000