Project Number Date
test_Tails_ISO_simplify-build-memory-requirements 3 14 May 2025, 22:22

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 19:40.099 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:57.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.052
When I start Tails from USB drive "old" with network unplugged 1:20.974
Then the boot device has safe access rights 3.540
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.839
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login 1:26.563
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 30.436
And I take note of which tps features are available 2.351
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.370
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.527
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.159
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.631
And I take note of which tps features are available 0.504
And I shutdown Tails and wait for the computer to power off 4.199
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.457
After features/support/hooks.rb:330 0.101
After features/support/hooks.rb:100 0.007
Tags: @product
2:54.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.226
And I log in to a new session 19.075
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.723
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.829
Then the running Tails is installed on USB drive "to_upgrade" 28.646
And I unplug USB drive "to_upgrade" 0.363
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 2.485
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.186
Then all tps features from the old Tails version are active 2.032
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.485
And all persistent directories from the old Tails version have safe access rights 2.562
After features/support/hooks.rb:330 0.869
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:43.276
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 14.264
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.571
When the network is plugged 0.082
And Tor is ready 26.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.517
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.198
Given I shutdown Tails and wait for the computer to power off 10.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.803
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.268
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.280
When the network is plugged 0.078
And Tor is ready 21.508
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.775
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.717
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.696
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.086
And Tor is ready 16.803
Then the Upgrader considers the system as up-to-date 0.320
# 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.603
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.432
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.291
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 10.334
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 23.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.231
After features/support/hooks.rb:330 1.302
After features/support/hooks.rb:100 0.000