Project Number Date
test_Tails_ISO_20619-wait-for-persistent-storage-check 1 22 Oct 2024, 20:24

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 18:46.968 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:8.560
Before features/support/hooks.rb:269 0.004
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.656
When I start Tails from USB drive "old" with network unplugged 1:33.818
Then the boot device has safe access rights 2.876
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.536
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.986
Before features/support/hooks.rb:269 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:20.550
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.406
And I take note of which tps features are available 1.514
Then a Tails persistence partition exists on USB drive "old" 0.769
And I shutdown Tails and wait for the computer to power off 8.263
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.833
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.750
Then Tails is running from USB drive "old" 0.954
And all tps features are active 1.849
When I write some files expected to persist 1.740
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.318
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.213
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.702
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.707
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 10.559
And I log in to a new session 20.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.556
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.582
Then the running Tails is installed on USB drive "to_upgrade" 17.019
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.611
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.050
Before features/support/hooks.rb:269 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.873
Then all tps features from the old Tails version are active 1.714
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.353
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.312
After features/support/hooks.rb:326 0.622
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:27.768
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 11.175
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.075
And Tor is ready 20.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.843
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.845
Given I shutdown Tails and wait for the computer to power off 8.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.394
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.341
When the network is plugged 0.089
And Tor is ready 18.100
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.949
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.954
Given I shutdown Tails and wait for the computer to power off 4.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.362
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.967
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.275
When the network is plugged 0.071
And Tor is ready 19.069
Then the Upgrader considers the system as up-to-date 10.875
# 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.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.817
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.060
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 9.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the signing key used by the Upgrader is outdated 0.721
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 19.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.337
After features/support/hooks.rb:326 0.789
After features/support/hooks.rb:100 0.000