Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 2 14 Dec 2024, 20:03

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:6.124 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:21.093
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.045
When I start Tails from USB drive "old" with network unplugged 1:44.261
Then the boot device has safe access rights 3.396
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.536
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.223
Before features/support/hooks.rb:269 0.005
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:36.140
Then Tails is running from USB drive "old" 0.441
And I create a persistent partition 32.154
And I take note of which tps features are available 1.986
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.017
Tags: @product
3:11.259
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.892
Then Tails is running from USB drive "old" 0.609
And all tps features are active 2.407
When I write some files expected to persist 2.120
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.339
And all persistence configuration files have safe access rights 0.574
And all persistent directories from the old Tails version have safe access rights 3.081
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.787
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.780
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.729
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 12.517
And I log in to a new session 21.379
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.970
And I plug USB drive "to_upgrade" 2.550
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.997
Then the running Tails is installed on USB drive "to_upgrade" 21.785
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.287
After features/support/hooks.rb:326 3.064
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.469
Before features/support/hooks.rb:269 0.005
Given a computer 0.239
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.336
Then all tps features from the old Tails version are active 1.657
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.342
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 3.996
After features/support/hooks.rb:326 1.048
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
6:35.532
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 12.047
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.085
And Tor is ready 22.396
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.157
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.480
Given I shutdown Tails and wait for the computer to power off 11.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.471
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.266
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.283
When the network is plugged 0.078
And Tor is ready 19.931
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.909
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.530
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.023
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.103
# 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.654
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.239
When the network is plugged 0.082
And Tor is ready 19.622
Then the Upgrader considers the system as up-to-date 0.388
# 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.691
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.333
After features/support/hooks.rb:326 0.820
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
37.816
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.770
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.891
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.225
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.000