Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 43 28 Apr 2025, 18:49

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 39:34.456 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:13.475
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 34.752
When I start Tails from USB drive "old" with network unplugged 1:33.120
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:335 6.978
After features/support/hooks.rb:105 0.033
Tags: @product
2:11.726
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:28.213
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.305
And I take note of which tps features are available 1.675
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 8.246
After features/support/hooks.rb:335 0.177
After features/support/hooks.rb:105 0.009
Tags: @product
2:55.907
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.499
Then Tails is running from USB drive "old" 0.444
And all tps features are active 1.837
When I write some files expected to persist 1.644
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.368
And all persistence configuration files have safe access rights 1.560
And all persistent directories from the old Tails version have safe access rights 2.506
And I take note of which tps features are available 0.401
And I shutdown Tails and wait for the computer to power off 6.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.033
After features/support/hooks.rb:335 0.106
After features/support/hooks.rb:105 0.009
Tags: @product
2:31.549
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 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.801
And I log in to a new session 19.154
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.930
And I plug USB drive "to_upgrade" 2.754
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.723
Then the running Tails is installed on USB drive "to_upgrade" 19.764
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:335 0.749
After features/support/hooks.rb:105 0.000
Tags: @product
21:56.997
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Steps
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 21:56.823
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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:335 10.857 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:54:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/43/artifact/build-artifacts/01:54:36_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/43/artifact/build-artifacts/01:54:36_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/43/artifact/build-artifacts/01:54:36_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
7:6.234
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.641
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.594
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.064
And Tor is ready 22.151
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.417
Given I shutdown Tails and wait for the computer to power off 8.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.417
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.383
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.301
When the network is plugged 0.177
And Tor is ready 16.876
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.265
Given I shutdown Tails and wait for the computer to power off 4.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.494
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.048
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.386
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.061
And Tor is ready 45.775
Then the Upgrader considers the system as up-to-date 0.316
# 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.257
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.638
After features/support/hooks.rb:335 0.776
After features/support/hooks.rb:105 0.016
Tags: @product @automatic_upgrade
38.564
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.936
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.677
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 21.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.697
After features/support/hooks.rb:335 0.860
After features/support/hooks.rb:105 0.000