Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 6 10 Mar 2025, 06:27

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:57.465 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:24.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.272
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.319
When I start Tails from USB drive "old" with network unplugged 1:48.039
Then the boot device has safe access rights 3.012
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 0.851
After features/support/hooks.rb:100 0.053
Tags: @product
2:13.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:28.019
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 35.799
And I take note of which tps features are available 1.728
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 6.579
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.011
Tags: @product
2:57.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.760
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.134
When I write some files expected to persist 2.373
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.476
And I take note of which tps features are available 0.504
And I shutdown Tails and wait for the computer to power off 4.409
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.654
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.411
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 11.123
And I log in to a new session 20.195
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.670
And I plug USB drive "to_upgrade" 2.355
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.182
Then the running Tails is installed on USB drive "to_upgrade" 18.344
And I unplug USB drive "to_upgrade" 0.304
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 0.941
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.868
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.384
And the boot device has safe access rights 3.687
And the expected persistent files created with the old Tails version are present in the filesystem 1.470
And all persistent directories from the old Tails version have safe access rights 2.327
After features/support/hooks.rb:330 1.717
After features/support/hooks.rb:100 0.210
Tags: @product @automatic_upgrade
6:57.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.053
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.466
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
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.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.642
When the network is plugged 0.066
And Tor is ready 23.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.428
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.717
Given I shutdown Tails and wait for the computer to power off 8.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.598
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 2.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.475
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.348
When the network is plugged 0.069
And Tor is ready 18.486
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.600
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.514
Given I shutdown Tails and wait for the computer to power off 4.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.107
Then Tails is running version 6.3~testoverlayfs 0.088
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.103
And Tor is ready 20.410
Then the Upgrader considers the system as up-to-date 0.321
# 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.098
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.023
After features/support/hooks.rb:330 0.829
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
39.363
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 with a persistent partition enabled and logged in 10.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 22.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.379
After features/support/hooks.rb:330 1.028
After features/support/hooks.rb:100 0.000