Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 7 31 Oct 2024, 12:36

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 21:11.817 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:41.019
Before features/support/hooks.rb:269 0.005
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.088
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 57.788
When I start Tails from USB drive "old" with network unplugged 1:37.584
Then the boot device has safe access rights 3.205
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.773
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.221
Before features/support/hooks.rb:269 0.004
Given a computer 1.597
And I start Tails from USB drive "old" with network unplugged and I login 1:22.459
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 34.061
And I take note of which tps features are available 2.054
Then a Tails persistence partition exists on USB drive "old" 0.959
And I shutdown Tails and wait for the computer to power off 8.727
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.011
Tags: @product
2:54.911
Before features/support/hooks.rb:269 0.005
Given a computer 0.965
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.708
Then Tails is running from USB drive "old" 0.785
And all tps features are active 2.163
When I write some files expected to persist 1.689
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
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.512
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.626
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.072
Before features/support/hooks.rb:269 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.145
And I log in to a new session 19.450
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.892
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.827
Then the running Tails is installed on USB drive "to_upgrade" 23.844
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 3.698
After features/support/hooks.rb:100 0.000
Tags: @product
2:52.659
Before features/support/hooks.rb:269 0.008
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:41.960
Then all tps features from the old Tails version are active 1.853
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.463
And all persistent directories from the old Tails version have safe access rights 3.436
After features/support/hooks.rb:326 0.874
After features/support/hooks.rb:100 0.010
7:17.778
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 28.412
And no SquashFS delta is installed 0.303
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.579
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.672
And Tor is ready 23.666
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.471
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.487
Given I shutdown Tails and wait for the computer to power off 9.338
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.725
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 3.428
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.300
When the network is plugged 0.097
And Tor is ready 16.937
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.318
Given I shutdown Tails and wait for the computer to power off 6.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.748
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.398
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.376
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.165
And Tor is ready 20.469
Then the Upgrader considers the system as up-to-date 0.339
# 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.545
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.254
After features/support/hooks.rb:326 1.064
After features/support/hooks.rb:100 0.019
37.154
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 12.330
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.798
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.781
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 16.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.024
After features/support/hooks.rb:326 1.248
After features/support/hooks.rb:100 0.000