Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 26 29 Mar 2025, 06:29

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:9.880 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:14.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 33.729
When I start Tails from USB drive "old" with network unplugged 1:35.102
Then the boot device has safe access rights 3.027
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.309
After features/support/hooks.rb:330 7.484
After features/support/hooks.rb:100 0.034
Tags: @product
2:12.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:25.499
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 34.919
And I take note of which tps features are available 1.805
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.422
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.283
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.915
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.360
And I take note of which tps features are available 0.567
And I shutdown Tails and wait for the computer to power off 4.274
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.932
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.810
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 9.548
And I log in to a new session 17.601
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.475
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.403
Then the running Tails is installed on USB drive "to_upgrade" 20.937
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 0.884
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.158
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.582
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.484
And the expected persistent files created with the old Tails version are present in the filesystem 1.422
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:330 1.310
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:22.313
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 10.713
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.725
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.065
And Tor is ready 20.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.679
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.218
Given I shutdown Tails and wait for the computer to power off 8.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.955
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.365
# 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.256
When the network is plugged 0.062
And Tor is ready 17.660
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.097
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.685
Given I shutdown Tails and wait for the computer to power off 59.086
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.580
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.950
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.449
When the network is plugged 0.081
And Tor is ready 16.400
Then the Upgrader considers the system as up-to-date 0.304
# 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.322
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.838
After features/support/hooks.rb:330 0.676
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.536
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.101
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.408
After features/support/hooks.rb:330 0.627
After features/support/hooks.rb:100 0.000