Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 27 24 Nov 2024, 11:57

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:45.913 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:39.909
Before features/support/hooks.rb:269 0.028
Given a computer 0.719
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 48.656
When I start Tails from USB drive "old" with network unplugged 1:44.813
Then the boot device has safe access rights 3.428
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 3.607
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.531
Before features/support/hooks.rb:269 0.006
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login 1:30.480
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 36.393
And I take note of which tps features are available 1.437
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.761
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.008
Tags: @product
3:6.804
Before features/support/hooks.rb:269 0.004
Given a computer 0.293
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.409
Then Tails is running from USB drive "old" 0.517
And all tps features are active 2.220
When I write some files expected to persist 1.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.886
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.203
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.038
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.150
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.832
And I log in to a new session 23.197
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.688
And I plug USB drive "to_upgrade" 2.588
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.525
Then the running Tails is installed on USB drive "to_upgrade" 24.846
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 1.198
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.858
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.077
Then all tps features from the old Tails version are active 1.774
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.476
After features/support/hooks.rb:326 0.881
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:47.526
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 13.672
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.388
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.599
When the network is plugged 0.449
And Tor is ready 21.199
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.094
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.329
Given I shutdown Tails and wait for the computer to power off 10.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.269
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.420
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.287
When the network is plugged 0.078
And Tor is ready 19.301
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.439
Given I shutdown Tails and wait for the computer to power off 4.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.852
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.743
And the file system changes introduced in version 6.3~testoverlayfs are present 0.711
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.395
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.112
And Tor is ready 22.190
Then the Upgrader considers the system as up-to-date 0.310
# 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.570
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.085
After features/support/hooks.rb:326 0.832
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.131
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 10.529
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
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.773
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 21.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.846
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.000