Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 16 11 Nov 2024, 12:41

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:34.827 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.294
Before features/support/hooks.rb:269 0.004
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 33.899
When I start Tails from USB drive "old" with network unplugged 1:44.303
Then the boot device has safe access rights 3.429
And Tails is running from USB drive "old" 0.449
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.498
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.777
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.116
Before features/support/hooks.rb:269 0.005
Given a computer 0.305
And I start Tails from USB drive "old" with network unplugged and I login 1:28.905
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 35.581
And I take note of which tps features are available 2.028
Then a Tails persistence partition exists on USB drive "old" 0.882
And I shutdown Tails and wait for the computer to power off 9.028
After features/support/hooks.rb:326 0.235
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.450
Before features/support/hooks.rb:269 0.013
Given a computer 0.330
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.554
Then Tails is running from USB drive "old" 0.452
And all tps features are active 2.294
When I write some files expected to persist 1.876
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.529
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.391
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.962
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.412
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.298
And I log in to a new session 21.965
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.886
And I plug USB drive "to_upgrade" 2.549
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.879
Then the running Tails is installed on USB drive "to_upgrade" 24.392
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 3.410
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.596
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.495
Then all tps features from the old Tails version are active 1.824
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.630
And the expected persistent files created with the old Tails version are present in the filesystem 2.330
And all persistent directories from the old Tails version have safe access rights 2.708
After features/support/hooks.rb:326 1.081
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:6.631
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 11.867
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.542
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.703
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.087
And Tor is ready 25.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.276
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.560
Given I shutdown Tails and wait for the computer to power off 11.169
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.373
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.501
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.112
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.505
# 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.291
When the network is plugged 0.075
And Tor is ready 19.825
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.500
Given I shutdown Tails and wait for the computer to power off 4.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.256
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.291
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.083
And Tor is ready 27.502
Then the Upgrader considers the system as up-to-date 0.316
# 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 14.986
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.234
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.323
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 11.574
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.528
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.931
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 20.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.470
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.000