Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 7 28 Oct 2024, 20:56

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 18:50.262 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:5.489
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 39.418
When I start Tails from USB drive "old" with network unplugged 1:20.678
Then the boot device has safe access rights 3.137
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.080
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.732
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:22.722
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 30.987
And I take note of which tps features are available 1.324
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 10.324
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.793
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.271
Then Tails is running from USB drive "old" 0.902
And all tps features are active 1.912
When I write some files expected to persist 1.603
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.431
And I take note of which tps features are available 0.387
And I shutdown Tails and wait for the computer to power off 4.501
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.998
After features/support/hooks.rb:326 0.089
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.942
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 10.696
And I log in to a new session 18.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.704
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.610
Then the running Tails is installed on USB drive "to_upgrade" 23.500
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:326 2.092
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.033
Before features/support/hooks.rb:269 0.006
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.561
Then all tps features from the old Tails version are active 1.576
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 2.837
And the expected persistent files created with the old Tails version are present in the filesystem 1.317
And all persistent directories from the old Tails version have safe access rights 2.263
After features/support/hooks.rb:326 0.571
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.660
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 11.296
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.066
And Tor is ready 20.237
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.338
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.085
Given I shutdown Tails and wait for the computer to power off 8.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.964
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.944
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.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.272
When the network is plugged 0.061
And Tor is ready 45.633
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.693
Given I shutdown Tails and wait for the computer to power off 4.135
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.188
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.961
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.068
And Tor is ready 16.515
Then the Upgrader considers the system as up-to-date 0.299
# 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 14.626
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.029
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.610
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 10.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.722
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 19.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.337
After features/support/hooks.rb:326 0.647
After features/support/hooks.rb:100 0.000