Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 13 08 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:22.523 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:17.814
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 32.119
When I start Tails from USB drive "old" with network unplugged 1:40.107
Then the boot device has safe access rights 3.223
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 0.990
After features/support/hooks.rb:100 0.057
Tags: @product
2:16.448
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:29.828
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 33.869
And I take note of which tps features are available 2.185
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 9.213
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.012
Tags: @product
3:2.398
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:14.109
Then Tails is running from USB drive "old" 1.091
And all tps features are active 6.880
When I write some files expected to persist 2.537
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.401
And I take note of which tps features are available 1.661
And I shutdown Tails and wait for the computer to power off 6.523
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.304
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.310
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 30.932
And I log in to a new session 19.286
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.992
And I plug USB drive "to_upgrade" 2.739
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.503
Then the running Tails is installed on USB drive "to_upgrade" 23.419
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.009
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.708
Before features/support/hooks.rb:269 0.007
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.761
Then all tps features from the old Tails version are active 2.003
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.307
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.567
After features/support/hooks.rb:326 1.146
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.006
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 14.012
And no SquashFS delta is installed 2.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.579
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.091
And Tor is ready 23.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.814
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.907
Given I shutdown Tails and wait for the computer to power off 11.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.024
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.297
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.296
When the network is plugged 0.079
And Tor is ready 21.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.214
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.919
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.727
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.094
And Tor is ready 22.053
Then the Upgrader considers the system as up-to-date 0.388
# 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 16.274
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.177
After features/support/hooks.rb:326 0.848
After features/support/hooks.rb:100 0.074
Tags: @product @automatic_upgrade
37.837
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.942
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.592
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.900
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 18.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.875
After features/support/hooks.rb:326 1.065
After features/support/hooks.rb:100 0.000