Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 7 19 Dec 2024, 20:41

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 23:47.032 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.978
Before features/support/hooks.rb:269 0.004
Given a computer 0.795
And I create a 7200 MiB disk named "old" 0.268
And I plug USB drive "old" 1.194
And I write an old version of the Tails USB image to disk "old" 33.704
When I start Tails from USB drive "old" with network unplugged 1:40.577
Then the boot device has safe access rights 3.324
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:326 7.162
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.251
Before features/support/hooks.rb:269 0.008
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:41.934
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 35.883
And I take note of which tps features are available 2.073
Then a Tails persistence partition exists on USB drive "old" 0.977
And I shutdown Tails and wait for the computer to power off 8.810
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.011
Tags: @product
3:18.269
Before features/support/hooks.rb:269 0.007
Given a computer 0.331
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.013
Then Tails is running from USB drive "old" 0.465
And all tps features are active 2.744
When I write some files expected to persist 2.203
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.757
And I take note of which tps features are available 0.752
And I shutdown Tails and wait for the computer to power off 4.261
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.964
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.270
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 24.548
And I log in to a new session 23.859
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.776
And I plug USB drive "to_upgrade" 2.511
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.673
Then the running Tails is installed on USB drive "to_upgrade" 28.430
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.379
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.020
Before features/support/hooks.rb:269 0.006
Given a computer 0.327
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.968
Then all tps features from the old Tails version are active 2.028
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.720
And the expected persistent files created with the old Tails version are present in the filesystem 1.709
And all persistent directories from the old Tails version have safe access rights 2.928
After features/support/hooks.rb:326 1.106
After features/support/hooks.rb:100 0.024
9:6.015
Before features/support/hooks.rb:269 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 44.095
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.471
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.379
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.114
And Tor is ready 24.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.861
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.118
Given I shutdown Tails and wait for the computer to power off 1:32.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.950
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.919
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.352
When the network is plugged 0.546
And Tor is ready 20.214
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.607
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.628
Given I shutdown Tails and wait for the computer to power off 4.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.906
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.912
And the file system changes introduced in version 6.3~testoverlayfs are present 0.603
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.445
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.332
When the network is plugged 0.094
And Tor is ready 18.778
Then the Upgrader considers the system as up-to-date 10.893
# 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.788
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.633
After features/support/hooks.rb:326 0.878
After features/support/hooks.rb:100 0.036
46.225
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.034
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the signing key used by the Upgrader is outdated 0.961
But a current signing key is available on our website 0.000
When the network is plugged 0.127
And Tor is ready 21.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.999
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.000