Project Number Date
test_Tails_ISO_simplify-build-memory-requirements 2 14 May 2025, 00:29

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 20:28.296 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
2:16.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 36.109
When I start Tails from USB drive "old" with network unplugged 1:35.063
Then the boot device has safe access rights 3.351
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:330 3.765
After features/support/hooks.rb:100 0.016
Tags: @product
2:12.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:27.628
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 32.749
And I take note of which tps features are available 1.990
Then a Tails persistence partition exists on USB drive "old" 0.915
And I shutdown Tails and wait for the computer to power off 9.100
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
2:57.686
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.232
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.147
When I write some files expected to persist 2.160
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.302
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.820
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.259
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.209
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.345
And I log in to a new session 19.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.729
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.042
Then the running Tails is installed on USB drive "to_upgrade" 26.930
And I unplug USB drive "to_upgrade" 0.341
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:330 6.865
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.581
Then all tps features from the old Tails version are active 1.924
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.624
And the expected persistent files created with the old Tails version are present in the filesystem 1.502
And all persistent directories from the old Tails version have safe access rights 2.515
After features/support/hooks.rb:330 1.781
After features/support/hooks.rb:100 0.010
7:10.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.705
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.128
And Tor is ready 23.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.740
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.735
Given I shutdown Tails and wait for the computer to power off 8.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.018
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.333
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.276
When the network is plugged 0.067
And Tor is ready 49.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.586
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.801
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.043
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.068
And Tor is ready 20.044
Then the Upgrader considers the system as up-to-date 0.335
# 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 15.469
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.610
After features/support/hooks.rb:330 0.732
After features/support/hooks.rb:100 0.032
38.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.889
After features/support/hooks.rb:330 1.776
After features/support/hooks.rb:100 0.000