Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 3 26 Oct 2024, 12:10

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 19:37.667 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:43.004
Before features/support/hooks.rb:269 0.005
Given a computer 0.325
And I create a 7200 MiB disk named "old" 0.181
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 49.854
When I start Tails from USB drive "old" with network unplugged 1:47.574
Then the boot device has safe access rights 3.025
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 0.924
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.983
Before features/support/hooks.rb:269 0.006
Given a computer 1.079
And I start Tails from USB drive "old" with network unplugged and I login 1:21.989
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 32.147
And I take note of which tps features are available 1.549
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.974
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
2:51.447
Before features/support/hooks.rb:269 0.003
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.771
Then Tails is running from USB drive "old" 1.245
And all tps features are active 2.603
When I write some files expected to persist 2.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.596
And all persistent directories from the old Tails version have safe access rights 2.692
And I take note of which tps features are available 0.519
And I shutdown Tails and wait for the computer to power off 4.375
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.611
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.405
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 12.060
And I log in to a new session 21.048
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.584
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.725
Then the running Tails is installed on USB drive "to_upgrade" 17.037
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 3.772
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.481
Before features/support/hooks.rb:269 0.007
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.228
Then all tps features from the old Tails version are active 1.788
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.263
And the expected persistent files created with the old Tails version are present in the filesystem 1.429
And all persistent directories from the old Tails version have safe access rights 2.257
After features/support/hooks.rb:326 1.069
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:33.591
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 12.169
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.063
And Tor is ready 22.369
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.476
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.573
Given I shutdown Tails and wait for the computer to power off 10.999
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.511
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.623
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.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.288
When the network is plugged 0.064
And Tor is ready 19.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.520
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.949
Given I shutdown Tails and wait for the computer to power off 4.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.399
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.071
And Tor is ready 17.768
Then the Upgrader considers the system as up-to-date 0.295
# 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.442
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.066
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.752
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.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.888
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.219
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.959
After features/support/hooks.rb:326 1.114
After features/support/hooks.rb:100 0.000