Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 24 21 Nov 2024, 12:01

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:44.562 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:15.057
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.487
When I start Tails from USB drive "old" with network unplugged 1:37.775
Then the boot device has safe access rights 3.382
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.656
After features/support/hooks.rb:100 0.015
Tags: @product
2:12.857
Before features/support/hooks.rb:269 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:28.775
Then Tails is running from USB drive "old" 0.451
And I create a persistent partition 31.665
And I take note of which tps features are available 1.783
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 9.167
After features/support/hooks.rb:326 0.194
After features/support/hooks.rb:100 0.010
Tags: @product
3:7.703
Before features/support/hooks.rb:269 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.182
Then Tails is running from USB drive "old" 1.398
And all tps features are active 2.418
When I write some files expected to persist 2.542
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 3.340
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.143
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.702
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.022
And I log in to a new session 19.742
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.459
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.821
Then the running Tails is installed on USB drive "to_upgrade" 24.754
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.589
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.391
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.675
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.374
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.570
After features/support/hooks.rb:326 0.920
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:37.813
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.676
And no SquashFS delta is installed 0.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.118
And Tor is ready 21.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.705
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.155
Given I shutdown Tails and wait for the computer to power off 11.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.595
Then Tails is running version 6.2~testoverlayfs 0.055
And all tps features are active 2.165
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.069
And Tor is ready 18.213
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.907
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.977
Given I shutdown Tails and wait for the computer to power off 4.720
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.445
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.130
And Tor is ready 19.459
Then the Upgrader considers the system as up-to-date 0.362
# 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.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.256
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.035
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 11.342
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 17.755
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.687
After features/support/hooks.rb:326 0.617
After features/support/hooks.rb:100 0.000