Project Number Date
test_Tails_ISO_simplify-build-memory-requirements 1 13 May 2025, 16:09

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:48.974 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:20.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.092
And I write an old version of the Tails USB image to disk "old" 31.649
When I start Tails from USB drive "old" with network unplugged 1:41.324
Then the boot device has safe access rights 4.626
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.456
And I unplug USB drive "old" 0.298
After features/support/hooks.rb:330 3.594
After features/support/hooks.rb:100 0.022
Tags: @product
2:15.038
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:30.768
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.797
And I take note of which tps features are available 2.068
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.985
After features/support/hooks.rb:330 0.200
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.084
Then Tails is running from USB drive "old" 1.462
And all tps features are active 2.248
When I write some files expected to persist 3.144
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.993
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 6.376
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.846
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.597
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 without a persistent partition and stopped at Tails Greeter's login screen 11.463
And I log in to a new session 21.951
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.621
And I plug USB drive "to_upgrade" 2.708
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.810
Then the running Tails is installed on USB drive "to_upgrade" 22.595
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 3.166
After features/support/hooks.rb:100 0.000
Tags: @product
2:38.833
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.194
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.302
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:330 1.692
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:3.130
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 with a persistent partition enabled and logged in 12.097
And no SquashFS delta is installed 0.392
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.067
And Tor is ready 22.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.664
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.863
Given I shutdown Tails and wait for the computer to power off 12.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.617
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.399
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.298
# 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.399
When the network is plugged 0.078
And Tor is ready 18.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.349
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.322
Given I shutdown Tails and wait for the computer to power off 4.578
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.274
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.415
And the file system changes introduced in version 6.3~testoverlayfs are present 0.598
And only the 6.3~testoverlayfs SquashFS delta is installed 0.121
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.079
And Tor is ready 19.785
Then the Upgrader considers the system as up-to-date 0.324
# 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 16.523
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.908
After features/support/hooks.rb:330 0.873
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
45.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.099
But a current signing key is available on our website 0.000
When the network is plugged 0.723
And Tor is ready 20.440
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.661
After features/support/hooks.rb:330 1.838
After features/support/hooks.rb:100 0.000