Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 26 23 Nov 2024, 11:57

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:40.218 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:14.960
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 32.805
When I start Tails from USB drive "old" with network unplugged 1:36.586
Then the boot device has safe access rights 3.182
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.281
Before features/support/hooks.rb:269 0.005
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:30.095
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 41.536
And I take note of which tps features are available 1.868
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 6.367
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.009
Tags: @product
3:18.273
Before features/support/hooks.rb:269 0.006
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.449
Then Tails is running from USB drive "old" 0.544
And all tps features are active 2.919
When I write some files expected to persist 2.021
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.571
And I take note of which tps features are available 2.570
And I shutdown Tails and wait for the computer to power off 6.270
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.002
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.768
Before features/support/hooks.rb:269 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 26.576
And I log in to a new session 21.869
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.318
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.165
Then the running Tails is installed on USB drive "to_upgrade" 25.936
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:326 2.329
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.147
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.819
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.677
And the expected persistent files created with the old Tails version are present in the filesystem 1.638
And all persistent directories from the old Tails version have safe access rights 2.719
After features/support/hooks.rb:326 1.147
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.672
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.263
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.119
And Tor is ready 20.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.062
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.498
Given I shutdown Tails and wait for the computer to power off 9.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.000
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.370
And the file system changes introduced in version 6.2~testoverlayfs are present 0.386
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.392
When the network is plugged 0.073
And Tor is ready 20.239
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.527
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.167
Given I shutdown Tails and wait for the computer to power off 5.039
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.239
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.062
And Tor is ready 18.423
Then the Upgrader considers the system as up-to-date 0.345
# 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.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.097
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.114
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.919
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.771
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 21.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.906
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.000