Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 31 31 Mar 2025, 22:13

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 38:17.661 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:1.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.550
When I start Tails from USB drive "old" with network unplugged 1:27.574
Then the boot device has safe access rights 2.991
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 6.956
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:32.189
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 32.378
And I take note of which tps features are available 1.340
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.220
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.357
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 "old" with network unplugged and I login with persistence enabled 2:14.241
Then Tails is running from USB drive "old" 0.356
And all tps features are active 1.846
When I write some files expected to persist 1.865
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.343
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.126
After features/support/hooks.rb:330 0.107
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.919
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 10.093
And I log in to a new session 18.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.696
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.677
Then the running Tails is installed on USB drive "to_upgrade" 23.305
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 0.781
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.028
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.832
Then all tps features from the old Tails version are active 1.595
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.175
And the expected persistent files created with the old Tails version are present in the filesystem 1.312
And all persistent directories from the old Tails version have safe access rights 2.595
After features/support/hooks.rb:330 1.319
After features/support/hooks.rb:100 0.009
25:41.865
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.573
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.442
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.059
And Tor is ready 23.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.070
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.472
Given I shutdown Tails and wait for the computer to power off 8.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.182
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.018
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.280
# 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.253
When the network is plugged 0.079
And Tor is ready 15.807
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.757
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.712
Given I shutdown Tails and wait for the computer to power off 4.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:56.257
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:62:in `read'
./features/support/helpers/remote_shell.rb:62:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:61:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:44:in `loop'
./features/support/helpers/remote_shell.rb:44:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:182:in `execute'
./features/support/helpers/remote_shell.rb:193:in `initialize'
./features/support/helpers/dogtail.rb:81:in `new'
./features/support/helpers/dogtail.rb:81:in `block in run'
./features/support/helpers/dogtail.rb:80:in `each'
./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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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 10.787

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:48)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/31/artifact/build-artifacts/02:14:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/31/artifact/build-artifacts/02:14:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/31/artifact/build-artifacts/02:14:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.017
41.679
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 12.276
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 22.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.486
After features/support/hooks.rb:330 0.923
After features/support/hooks.rb:100 0.000