Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 23 08 Nov 2024, 19:35

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:35.961 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:7.449
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.505
When I start Tails from USB drive "old" with network unplugged 1:32.824
Then the boot device has safe access rights 2.871
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.003
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.020
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:21.846
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 31.946
And I take note of which tps features are available 1.483
Then a Tails persistence partition exists on USB drive "old" 0.882
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.863
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.158
Then Tails is running from USB drive "old" 0.451
And all tps features are active 2.007
When I write some files expected to persist 1.957
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 3.000
And I take note of which tps features are available 0.608
And I shutdown Tails and wait for the computer to power off 4.369
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.411
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.567
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.278
And I log in to a new session 21.857
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.827
Then the running Tails is installed on USB drive "to_upgrade" 22.146
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 1.836
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.307
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.711
Then all tps features from the old Tails version are active 1.828
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.205
And the expected persistent files created with the old Tails version are present in the filesystem 1.704
And all persistent directories from the old Tails version have safe access rights 2.316
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.032
6:47.647
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.256
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.216
And Tor is ready 48.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.551
Given I shutdown Tails and wait for the computer to power off 8.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.605
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 4.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.282
When the network is plugged 0.071
And Tor is ready 20.150
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.277
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.923
Given I shutdown Tails and wait for the computer to power off 4.705
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.327
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.112
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.378
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.085
And Tor is ready 19.640
Then the Upgrader considers the system as up-to-date 0.331
# 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.219
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.991
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.013
42.106
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.833
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 19.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.325
After features/support/hooks.rb:326 0.654
After features/support/hooks.rb:100 0.000