Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 12 16 Mar 2025, 07:25

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 36:11.459 Failed
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:9.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 34.944
When I start Tails from USB drive "old" with network unplugged 1:28.216
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.557
After features/support/hooks.rb:330 3.699
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:31.176
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 30.923
And I take note of which tps features are available 1.788
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.711
After features/support/hooks.rb:330 0.243
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.825
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.594
Then Tails is running from USB drive "old" 0.565
And all tps features are active 2.562
When I write some files expected to persist 3.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 4.611
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.944
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.833
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 without a persistent partition and stopped at Tails Greeter's login screen 14.994
And I log in to a new session 18.947
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.812
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.941
Then the running Tails is installed on USB drive "to_upgrade" 22.189
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:330 2.116
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.392
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.297
Then all tps features from the old Tails version are active 1.682
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.238
And the expected persistent files created with the old Tails version are present in the filesystem 1.696
And all persistent directories from the old Tails version have safe access rights 2.859
After features/support/hooks.rb:330 0.952
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
23:8.453
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.768
And no SquashFS delta is installed 0.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.610
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.410
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.185
And Tor is ready 21.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.232
Given I shutdown Tails and wait for the computer to power off 8.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:4.933
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 11.061 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:17:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/02:17:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/02:17:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/02:17:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
42.702
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 with a persistent partition enabled and logged in 11.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.170
And Tor is ready 28.533
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.169
After features/support/hooks.rb:330 0.707
After features/support/hooks.rb:100 0.000