Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 46 18 Apr 2025, 06:54

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 22:22.022 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.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.281
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 59.597
When I start Tails from USB drive "old" with network unplugged 1:42.344
Then the boot device has safe access rights 3.807
And Tails is running from USB drive "old" 0.501
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.305
After features/support/hooks.rb:330 3.815
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.170
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:35.028
Then Tails is running from USB drive "old" 0.490
And I create a persistent partition 41.127
And I take note of which tps features are available 4.925
Then a Tails persistence partition exists on USB drive "old" 1.099
And I shutdown Tails and wait for the computer to power off 9.258
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.843
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.732
Then Tails is running from USB drive "old" 0.488
And all tps features are active 2.343
When I write some files expected to persist 1.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.288
And I take note of which tps features are available 0.668
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.042
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 25.042
And I log in to a new session 21.059
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.798
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.964
Then the running Tails is installed on USB drive "to_upgrade" 27.972
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 2.290
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.405
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.057
Then all tps features from the old Tails version are active 1.827
And Tails is running from USB drive "to_upgrade" 0.436
And the boot device has safe access rights 3.941
And the expected persistent files created with the old Tails version are present in the filesystem 1.648
And all persistent directories from the old Tails version have safe access rights 3.208
After features/support/hooks.rb:330 2.169
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:42.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.571
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.735
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.085
And Tor is ready 22.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.659
Given I shutdown Tails and wait for the computer to power off 11.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.479
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.803
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.320
When the network is plugged 0.104
And Tor is ready 21.417
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.832
Given I shutdown Tails and wait for the computer to power off 6.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.998
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.701
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.085
And Tor is ready 17.583
Then the Upgrader considers the system as up-to-date 10.957
# 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 16.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.502
After features/support/hooks.rb:330 0.813
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
44.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.560
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.729
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 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.117
And Tor is ready 20.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.334
After features/support/hooks.rb:330 1.004
After features/support/hooks.rb:100 0.000