Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 15 02 Aug 2024, 16:31

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 20:48.012 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:48.616
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:5.867
When I start Tails from USB drive "old" with network unplugged 1:36.949
Then the boot device has safe access rights 3.279
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:326 7.140
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.074
Before features/support/hooks.rb:269 0.006
Given a computer 0.295
And I start Tails from USB drive "old" with network unplugged and I login 1:23.788
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.910
And I take note of which tps features are available 1.942
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 7.969
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.087
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.083
Then Tails is running from USB drive "old" 0.698
And all tps features are active 2.160
When I write some files expected to persist 1.961
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.538
And all persistent directories from the old Tails version have safe access rights 2.787
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 4.357
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.484
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.811
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.920
And I log in to a new session 22.560
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.425
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.898
Then the running Tails is installed on USB drive "to_upgrade" 23.027
And I unplug USB drive "to_upgrade" 0.274
And I unplug USB drive "__internal" 0.277
After features/support/hooks.rb:326 2.636
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.885
Before features/support/hooks.rb:269 0.008
Given a computer 0.267
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.146
Then all tps features from the old Tails version are active 1.713
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.224
And the expected persistent files created with the old Tails version are present in the filesystem 1.658
And all persistent directories from the old Tails version have safe access rights 2.522
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:19.338
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 11.075
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.738
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.162
And Tor is ready 49.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.616
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.456
Given I shutdown Tails and wait for the computer to power off 9.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.039
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.552
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.423
# 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.378
When the network is plugged 0.075
And Tor is ready 46.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.854
Given I shutdown Tails and wait for the computer to power off 4.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.546
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.081
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.336
When the network is plugged 0.069
And Tor is ready 21.666
Then the Upgrader considers the system as up-to-date 0.350
# 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.251
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.114
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
40.199
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.352
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.057
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 20.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.801
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.000