Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 38 23 Nov 2024, 20:05

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:7.810 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:24.859
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.285
When I start Tails from USB drive "old" with network unplugged 1:46.086
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.557
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.433
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:29.280
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.190
And I take note of which tps features are available 1.828
Then a Tails persistence partition exists on USB drive "old" 0.964
And I shutdown Tails and wait for the computer to power off 8.626
After features/support/hooks.rb:326 0.238
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.866
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.315
Then Tails is running from USB drive "old" 0.523
And all tps features are active 2.004
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 3.214
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.395
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.336
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.015
Tags: @product
2:40.917
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 12.348
And I log in to a new session 20.885
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.526
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.833
Then the running Tails is installed on USB drive "to_upgrade" 25.380
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:326 7.119
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.480
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.383
Then all tps features from the old Tails version are active 1.745
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.436
And the expected persistent files created with the old Tails version are present in the filesystem 1.667
And all persistent directories from the old Tails version have safe access rights 2.679
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.009
6:46.005
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 13.381
And no SquashFS delta is installed 0.632
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.440
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.086
And Tor is ready 23.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.514
Given I shutdown Tails and wait for the computer to power off 12.709
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.340
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
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.347
# 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.331
When the network is plugged 0.083
And Tor is ready 23.052
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.409
Given I shutdown Tails and wait for the computer to power off 4.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.397
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.021
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.349
When the network is plugged 0.086
And Tor is ready 18.516
Then the Upgrader considers the system as up-to-date 0.394
# 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.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.028
After features/support/hooks.rb:326 0.830
After features/support/hooks.rb:100 0.018
42.247
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 11.221
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.943
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.850
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 23.971
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.102
After features/support/hooks.rb:326 0.964
After features/support/hooks.rb:100 0.000