Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 37 23 Aug 2024, 16:33

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:35.411 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:10.992
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.139
When I start Tails from USB drive "old" with network unplugged 1:34.739
Then the boot device has safe access rights 2.894
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 1.001
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.473
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:27.139
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.932
And I take note of which tps features are available 1.779
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 8.276
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.095
Before features/support/hooks.rb:269 0.006
Given a computer 0.326
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.957
Then Tails is running from USB drive "old" 1.443
And all tps features are active 2.065
When I write some files expected to persist 1.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 1.484
And all persistent directories from the old Tails version have safe access rights 3.576
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 4.047
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.830
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.787
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.147
And I log in to a new session 23.599
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.865
Then the running Tails is installed on USB drive "to_upgrade" 20.658
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 3.029
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.560
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.374
Then all tps features from the old Tails version are active 1.868
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.102
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.336
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:42.583
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.256
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.076
And Tor is ready 20.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.086
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.231
Given I shutdown Tails and wait for the computer to power off 11.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.705
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.315
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.289
When the network is plugged 0.075
And Tor is ready 18.023
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.669
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.116
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.328
When the network is plugged 0.084
And Tor is ready 18.915
Then the Upgrader considers the system as up-to-date 0.317
# 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.992
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.977
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
44.917
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.509
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.825
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 22.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.725
After features/support/hooks.rb:326 0.911
After features/support/hooks.rb:100 0.000