Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 18 14 Nov 2024, 11:58

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:30.418 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:48.502
Before features/support/hooks.rb:269 0.004
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.085
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:6.902
When I start Tails from USB drive "old" with network unplugged 1:36.069
Then the boot device has safe access rights 3.071
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 7.978
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.319
Before features/support/hooks.rb:269 0.005
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 1:28.644
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 31.007
And I take note of which tps features are available 1.964
Then a Tails persistence partition exists on USB drive "old" 1.615
And I shutdown Tails and wait for the computer to power off 8.433
After features/support/hooks.rb:326 0.222
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.478
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.998
Then Tails is running from USB drive "old" 1.475
And all tps features are active 2.072
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 3.757
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.256
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.710
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.018
Tags: @product
2:39.913
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 11.610
And I log in to a new session 23.696
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.732
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.415
Then the running Tails is installed on USB drive "to_upgrade" 23.390
And I unplug USB drive "to_upgrade" 0.290
And I unplug USB drive "__internal" 0.299
After features/support/hooks.rb:326 2.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.663
Before features/support/hooks.rb:269 0.005
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.216
Then all tps features from the old Tails version are active 1.635
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.334
And the expected persistent files created with the old Tails version are present in the filesystem 1.465
And all persistent directories from the old Tails version have safe access rights 2.378
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:52.236
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.556
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.507
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.232
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.637
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.071
And Tor is ready 21.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.944
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.994
Given I shutdown Tails and wait for the computer to power off 9.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.046
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.574
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.341
When the network is plugged 0.074
And Tor is ready 22.226
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.250
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.815
Given I shutdown Tails and wait for the computer to power off 4.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.330
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.069
And Tor is ready 16.695
Then the Upgrader considers the system as up-to-date 0.318
# 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.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.037
After features/support/hooks.rb:326 0.822
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
44.305
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.625
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 1.051
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 22.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.221
After features/support/hooks.rb:326 0.915
After features/support/hooks.rb:100 0.000