Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 39 23 Aug 2024, 20:17

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:49.052 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:18.784
Before features/support/hooks.rb:269 0.007
Given a computer 0.274
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.297
When I start Tails from USB drive "old" with network unplugged 1:40.365
Then the boot device has safe access rights 3.611
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.259
After features/support/hooks.rb:326 3.570
After features/support/hooks.rb:100 0.013
Tags: @product
2:11.530
Before features/support/hooks.rb:269 0.008
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:25.400
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 33.696
And I take note of which tps features are available 1.587
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 9.180
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.919
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.034
Then Tails is running from USB drive "old" 0.372
And all tps features are active 2.284
When I write some files expected to persist 1.911
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.336
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.768
And I take note of which tps features are available 0.525
And I shutdown Tails and wait for the computer to power off 6.702
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.235
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.136
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.156
And I log in to a new session 19.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.752
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.005
Then the running Tails is installed on USB drive "to_upgrade" 20.379
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 3.775
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.468
Before features/support/hooks.rb:269 0.008
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.799
Then all tps features from the old Tails version are active 1.801
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.848
And the expected persistent files created with the old Tails version are present in the filesystem 1.667
And all persistent directories from the old Tails version have safe access rights 2.731
After features/support/hooks.rb:326 1.125
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:52.349
Before features/support/hooks.rb:269 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.375
And no SquashFS delta is installed 0.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.495
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.069
And Tor is ready 24.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.122
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.745
Given I shutdown Tails and wait for the computer to power off 8.859
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.583
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.400
When the network is plugged 0.095
And Tor is ready 18.697
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.890
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.395
Given I shutdown Tails and wait for the computer to power off 4.616
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.159
Then Tails is running version 6.3~testoverlayfs 0.035
And all tps features are active 2.513
And the file system changes introduced in version 6.3~testoverlayfs are present 0.609
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.074
And Tor is ready 20.826
Then the Upgrader considers the system as up-to-date 0.503
# 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.864
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.183
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
38.862
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.397
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.058
And the signing key used by the Upgrader is outdated 0.956
But a current signing key is available on our website 0.000
When the network is plugged 0.198
And Tor is ready 18.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.066
After features/support/hooks.rb:326 1.652
After features/support/hooks.rb:100 0.000