Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 31 16 Nov 2024, 20:25

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 22:15.644 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
3:12.419
Before features/support/hooks.rb:269 0.005
Given a computer 0.387
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 1:11.066
When I start Tails from USB drive "old" with network unplugged 1:55.032
Then the boot device has safe access rights 3.699
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.576
After features/support/hooks.rb:100 0.011
Tags: @product
2:22.350
Before features/support/hooks.rb:269 0.005
Given a computer 0.282
And I start Tails from USB drive "old" with network unplugged and I login 1:32.727
Then Tails is running from USB drive "old" 0.465
And I create a persistent partition 35.631
And I take note of which tps features are available 2.249
Then a Tails persistence partition exists on USB drive "old" 1.041
And I shutdown Tails and wait for the computer to power off 9.952
After features/support/hooks.rb:326 0.255
After features/support/hooks.rb:100 0.013
Tags: @product
3:8.318
Before features/support/hooks.rb:269 0.007
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.341
Then Tails is running from USB drive "old" 0.364
And all tps features are active 3.011
When I write some files expected to persist 2.114
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.903
And I take note of which tps features are available 0.699
And I shutdown Tails and wait for the computer to power off 4.336
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.564
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.012
Tags: @product
3:1.674
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.220
And I log in to a new session 22.914
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.113
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.301
Then the running Tails is installed on USB drive "to_upgrade" 26.697
And I unplug USB drive "to_upgrade" 0.437
And I unplug USB drive "__internal" 0.525
After features/support/hooks.rb:326 3.409
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.151
Before features/support/hooks.rb:269 0.004
Given a computer 0.383
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.588
Then all tps features from the old Tails version are active 2.021
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.553
And all persistent directories from the old Tails version have safe access rights 2.811
After features/support/hooks.rb:326 0.996
After features/support/hooks.rb:100 0.012
7:15.067
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 27.840
And no SquashFS delta is installed 0.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.087
And Tor is ready 24.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.705
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.995
Given I shutdown Tails and wait for the computer to power off 11.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.200
Then Tails is running version 6.2~testoverlayfs 0.049
And all tps features are active 2.758
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.372
When the network is plugged 0.088
And Tor is ready 19.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.857
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.612
Given I shutdown Tails and wait for the computer to power off 4.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.829
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.314
And the file system changes introduced in version 6.3~testoverlayfs are present 0.723
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.429
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.069
And Tor is ready 16.832
Then the Upgrader considers the system as up-to-date 0.354
# 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.362
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.175
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.019
42.661
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.455
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
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.825
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 21.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.507
After features/support/hooks.rb:326 0.919
After features/support/hooks.rb:100 0.000