Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 6 18 Dec 2024, 21:43

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:3.742 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:15.930
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.094
And I write an old version of the Tails USB image to disk "old" 32.685
When I start Tails from USB drive "old" with network unplugged 1:37.547
Then the boot device has safe access rights 3.314
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.731
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.610
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:26.029
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.207
And I take note of which tps features are available 1.567
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 6.454
After features/support/hooks.rb:326 0.229
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.399
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.409
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.213
When I write some files expected to persist 1.844
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.845
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.586
And I take note of which tps features are available 0.560
And I shutdown Tails and wait for the computer to power off 4.370
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.546
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.565
Before features/support/hooks.rb:269 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.755
And I log in to a new session 21.419
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.859
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.316
Then the running Tails is installed on USB drive "to_upgrade" 26.299
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.256
After features/support/hooks.rb:326 1.936
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.658
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.780
Then all tps features from the old Tails version are active 2.038
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.831
And the expected persistent files created with the old Tails version are present in the filesystem 1.636
And all persistent directories from the old Tails version have safe access rights 2.825
After features/support/hooks.rb:326 0.922
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:43.199
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 13.304
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.115
And Tor is ready 20.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.253
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.602
Given I shutdown Tails and wait for the computer to power off 10.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.740
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.709
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
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.338
# 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.338
When the network is plugged 0.103
And Tor is ready 19.087
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.994
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.642
Given I shutdown Tails and wait for the computer to power off 4.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.889
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.579
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.447
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.167
And Tor is ready 19.453
Then the Upgrader considers the system as up-to-date 0.317
# 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.193
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.169
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.378
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 10.526
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.754
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 21.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.991
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.000