Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 5 08 Mar 2025, 06:25

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 18:52.087 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
1:56.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.742
When I start Tails from USB drive "old" with network unplugged 1:20.309
Then the boot device has safe access rights 2.896
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 6.856
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:20.854
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 31.970
And I take note of which tps features are available 1.442
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.638
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.880
Then Tails is running from USB drive "old" 0.408
And all tps features are active 1.793
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.245
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.234
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 4.171
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.328
After features/support/hooks.rb:330 0.092
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.258
And I log in to a new session 17.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.295
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.286
Then the running Tails is installed on USB drive "to_upgrade" 16.543
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 6.634
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.000
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.016
Then all tps features from the old Tails version are active 1.558
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.166
And the expected persistent files created with the old Tails version are present in the filesystem 1.393
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:330 0.567
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.229
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 10.609
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.586
When the network is plugged 0.060
And Tor is ready 21.209
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.244
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.354
Given I shutdown Tails and wait for the computer to power off 8.711
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.699
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.140
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.269
When the network is plugged 0.080
And Tor is ready 19.858
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.031
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.518
Given I shutdown Tails and wait for the computer to power off 4.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.074
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.138
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.072
And Tor is ready 16.375
Then the Upgrader considers the system as up-to-date 0.385
# 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.676
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.032
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
58.822
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.507
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 48.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.587
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.000