Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 16 03 Nov 2024, 19:37

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 19:34.087 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:8.968
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.943
When I start Tails from USB drive "old" with network unplugged 1:32.388
Then the boot device has safe access rights 3.305
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 7.214
After features/support/hooks.rb:100 0.029
Tags: @product
2:11.561
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:28.463
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 31.447
And I take note of which tps features are available 1.903
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.328
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.284
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.301
Then Tails is running from USB drive "old" 0.463
And all tps features are active 2.146
When I write some files expected to persist 1.634
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.551
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.389
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.478
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.811
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 11.520
And I log in to a new session 20.015
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.786
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.097
Then the running Tails is installed on USB drive "to_upgrade" 21.468
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 1.822
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.794
Before features/support/hooks.rb:269 0.005
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.254
Then all tps features from the old Tails version are active 2.017
And Tails is running from USB drive "to_upgrade" 0.441
And the boot device has safe access rights 3.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.567
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.009
6:52.107
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 26.337
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
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.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.080
And Tor is ready 20.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.635
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.101
Given I shutdown Tails and wait for the computer to power off 12.681
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.538
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.619
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.401
# 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.270
When the network is plugged 0.104
And Tor is ready 20.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.667
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.860
Given I shutdown Tails and wait for the computer to power off 6.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.769
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.218
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.074
And Tor is ready 17.414
Then the Upgrader considers the system as up-to-date 10.914
# 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.469
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.953
After features/support/hooks.rb:326 0.804
After features/support/hooks.rb:100 0.017
37.559
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.804
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 18.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.515
After features/support/hooks.rb:326 0.864
After features/support/hooks.rb:100 0.000