Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 5 17 Dec 2024, 20:01

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 21:33.665 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:44.346
Before features/support/hooks.rb:269 0.006
Given a computer 2.281
And I create a 7200 MiB disk named "old" 0.764
And I plug USB drive "old" 1.239
And I write an old version of the Tails USB image to disk "old" 46.264
When I start Tails from USB drive "old" with network unplugged 1:48.819
Then the boot device has safe access rights 3.644
And Tails is running from USB drive "old" 0.470
And there is no persistence partition on USB drive "old" 0.134
And process "udev-watchdog" is running 0.136
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:326 3.860
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.112
Before features/support/hooks.rb:269 0.008
Given a computer 0.408
And I start Tails from USB drive "old" with network unplugged and I login 1:30.008
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 33.734
And I take note of which tps features are available 2.220
Then a Tails persistence partition exists on USB drive "old" 1.003
And I shutdown Tails and wait for the computer to power off 9.407
After features/support/hooks.rb:326 0.294
After features/support/hooks.rb:100 0.013
Tags: @product
3:5.105
Before features/support/hooks.rb:269 0.008
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.224
Then Tails is running from USB drive "old" 0.411
And all tps features are active 2.450
When I write some files expected to persist 2.041
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.579
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.562
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.013
Tags: @product
2:40.201
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 10.259
And I log in to a new session 21.237
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.037
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.275
Then the running Tails is installed on USB drive "to_upgrade" 26.519
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.794
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.937
Before features/support/hooks.rb:269 0.007
Given a computer 0.317
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.556
Then all tps features from the old Tails version are active 2.226
And Tails is running from USB drive "to_upgrade" 0.420
And the boot device has safe access rights 3.991
And the expected persistent files created with the old Tails version are present in the filesystem 1.572
And all persistent directories from the old Tails version have safe access rights 2.853
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.013
7:15.998
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 15.049
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.525
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.082
And Tor is ready 24.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.053
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.486
Given I shutdown Tails and wait for the computer to power off 11.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.082
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 5.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.408
When the network is plugged 0.104
And Tor is ready 17.621
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.166
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.536
Given I shutdown Tails and wait for the computer to power off 6.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.178
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.090
And Tor is ready 20.996
Then the Upgrader considers the system as up-to-date 0.328
# 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.643
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.052
After features/support/hooks.rb:326 0.828
After features/support/hooks.rb:100 0.017
1:5.964
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 14.706
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.908
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 49.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.620
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.000