Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 36 23 Aug 2024, 14:50

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.366 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.550
Before features/support/hooks.rb:269 0.008
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.995
When I start Tails from USB drive "old" with network unplugged 2:3.990
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.097
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 0.921
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.136
Before features/support/hooks.rb:269 0.009
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:28.132
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 31.647
And I take note of which tps features are available 2.233
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 10.646
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.598
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.172
Then Tails is running from USB drive "old" 0.386
And all tps features are active 2.346
When I write some files expected to persist 1.743
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.430
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.660
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.467
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.305
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.890
And I log in to a new session 20.207
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.468
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.533
Then the running Tails is installed on USB drive "to_upgrade" 20.346
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.518
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.736
Before features/support/hooks.rb:269 0.029
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.382
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 4.255
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.350
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:19.406
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.235
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.084
And Tor is ready 20.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.411
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.780
Given I shutdown Tails and wait for the computer to power off 10.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.701
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.268
When the network is plugged 0.086
And Tor is ready 18.443
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.325
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.686
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.282
And the file system changes introduced in version 6.3~testoverlayfs are present 0.606
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.519
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.071
And Tor is ready 19.184
Then the Upgrader considers the system as up-to-date 0.357
# 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.911
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.025
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.633
Before features/support/hooks.rb:269 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.010
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
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.742
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 17.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.944
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.000