Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 103 26 Jun 2025, 21:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 62 3 22 0 0 87 4 3 7 30:53.414 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
4:2.743
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.012
Given a computer 0.361
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 59.493
When I start Tails from USB drive "old" with network unplugged 2:55.711
Then the boot device has safe access rights 4.690
And Tails is running from USB drive "old" 0.470
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.165
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.347
After features/support/hooks.rb:335 9.474
After features/support/hooks.rb:105 0.175
Tags: @product
4:20.899
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.090
Given a computer 2.904
And I start Tails from USB drive "old" with network unplugged and I login 2:40.479
Then Tails is running from USB drive "old" 0.985
And I create a persistent partition 1:14.909
And I take note of which tps features are available 5.249
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 15.542
After features/support/hooks.rb:335 0.594
After features/support/hooks.rb:105 0.028
Tags: @product
5:29.785
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.028
Given a computer 1.833
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:5.979
Then Tails is running from USB drive "old" 1.244
And all tps features are active 4.883
When I write some files expected to persist 7.227
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.858
And all persistence configuration files have safe access rights 0.791
And all persistent directories from the old Tails version have safe access rights 2.745
And I take note of which tps features are available 0.715
And I shutdown Tails and wait for the computer to power off 16.920
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 46.586
After features/support/hooks.rb:335 0.156
After features/support/hooks.rb:105 0.010
Tags: @product
3:36.653
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 21.349
And I log in to a new session 3:15.303
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/usb_upgrade.feature:62:in `And I log in to a new session'
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.000
And I plug USB drive "to_upgrade" 0.000
When I upgrade Tails to USB drive "to_upgrade" by cloning 0.000
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:335 13.932 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:35:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:35:24_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:35:24_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:35:24_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:35:24_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:105 0.000
Tags: @product
1.462
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.046
Steps
Given a computer 1.366
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.095
Call 
Call to virStorageVolLookupByName failed: Storage volume not found: no storage vol with matching name 'to_upgrade' (Libvirt::RetrieveError)
./features/support/helpers/storage_helper.rb:151:in `lookup_volume_by_name'
./features/support/helpers/storage_helper.rb:151:in `disk_path'
./features/support/helpers/vm_helper.rb:337:in `plug_drive'
./features/support/helpers/vm_helper.rb:416:in `set_disk_boot'
./features/step_definitions/common_steps.rb:144:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:282: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
Hooks
After features/support/hooks.rb:335 4.459
Error message 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:460:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:455:in `each'
./features/support/hooks.rb:455:in `After'
Output 1 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:35:40)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:35:40_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/103/artifact/build-artifacts/02:35:40_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:105 0.000
Tags: @product @automatic_upgrade
11:19.435
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.963
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.002
And the file system changes introduced in version 6.3~testoverlayfs are not present 6.996
When the network is plugged 3.857
And Tor is ready 41.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.948
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 27.010
Given I shutdown Tails and wait for the computer to power off 18.771
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:9.190
Then Tails is running version 6.2~testoverlayfs 1.138
And all tps features are active 10.783
And the file system changes introduced in version 6.2~testoverlayfs are present 0.398
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.480
# 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.302
When the network is plugged 0.100
And Tor is ready 40.244
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 23.227
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 36.267
Given I shutdown Tails and wait for the computer to power off 16.971
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.903
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:335 14.320 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:47:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:47:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:47:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/02:47:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.275
Tags: @product @automatic_upgrade
2:2.434
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.041
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 51.758
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 4.596
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.540
And the signing key used by the Upgrader is outdated 1.513
But a current signing key is available on our website 0.000
When the network is plugged 1.544
And Tor is ready 46.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 16.048
After features/support/hooks.rb:335 1.241
After features/support/hooks.rb:105 0.000