Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 118 14 Jul 2025, 21:22

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 73 3 11 0 0 87 4 3 7 38:44.133 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:25.413
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.024
Given a computer 0.527
And I create a 7200 MiB disk named "old" 0.099
And I plug USB drive "old" 1.098
And I write an old version of the Tails USB image to disk "old" 1:18.016
When I start Tails from USB drive "old" with network unplugged 2:56.279
Then the boot device has safe access rights 7.186
And Tails is running from USB drive "old" 0.954
And there is no persistence partition on USB drive "old" 0.143
And process "udev-watchdog" is running 0.225
And udev-watchdog is monitoring the correct device 0.651
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:335 8.555
After features/support/hooks.rb:105 0.196
Tags: @product
4:45.720
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.167
Given a computer 1.439
And I start Tails from USB drive "old" with network unplugged and I login 3:6.964
Then Tails is running from USB drive "old" 1.082
And I create a persistent partition 1:17.752
And I take note of which tps features are available 3.242
Then a Tails persistence partition exists on USB drive "old" 1.247
And I shutdown Tails and wait for the computer to power off 13.991
After features/support/hooks.rb:335 0.245
After features/support/hooks.rb:105 0.020
Tags: @product
5:11.397
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.017
Steps
Given a computer 0.366
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 5:11.030
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:335 8.533 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:23:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:23:17_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:23:17_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:23:17_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:23:17_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:105 0.014
Tags: @product
5:24.238
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 49.254
And I log in to a new session 52.032
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.387
And I plug USB drive "to_upgrade" 4.785
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:47.395
Then the running Tails is installed on USB drive "to_upgrade" 46.498
And I unplug USB drive "to_upgrade" 0.475
And I unplug USB drive "__internal" 0.410
After features/support/hooks.rb:335 1.542
After features/support/hooks.rb:105 0.000
Tags: @product
4:36.276
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.009
Steps
Given a computer 0.299
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:17.516
Then all tps features from the old Tails version are active 2.642
And Tails is running from USB drive "to_upgrade" 2.758
And the boot device has safe access rights 12.990
And the expected persistent files created with the old Tails version are present in the filesystem 0.068
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:21:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1097:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1096:in `each'
./features/step_definitions/usb.rb:1096:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:335 10.599 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:33:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:33:25_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:33:25_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/118/artifact/build-artifacts/02:33:25_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/118/artifact/build-artifacts/02:33:25_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:105 0.071
Tags: @product @automatic_upgrade
13:27.177
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.086
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 42.401
And no SquashFS delta is installed 1.826
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.539
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.464
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.626
When the network is plugged 0.095
And Tor is ready 39.420
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.565
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 33.628
Given I shutdown Tails and wait for the computer to power off 16.748
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:47.480
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 9.194
And the file system changes introduced in version 6.2~testoverlayfs are present 3.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.465
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 1.055
# 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.524
When the network is plugged 0.086
And Tor is ready 42.067
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.915
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 26.851
Given I shutdown Tails and wait for the computer to power off 7.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:1.067
Then Tails is running version 6.3~testoverlayfs 1.198
And all tps features are active 10.047
And the file system changes introduced in version 6.3~testoverlayfs are present 0.902
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.067
And Tor is ready 38.695
Then the Upgrader considers the system as up-to-date 0.691
# 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 35.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 5.157
After features/support/hooks.rb:335 1.190
After features/support/hooks.rb:105 0.151
Tags: @product @automatic_upgrade
53.909
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.023
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 35.530
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 16.812
try_for() 
try_for() timeout expired (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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:335 5.878 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:48:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:48:00_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:48:00_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:48:00_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/02:48:00_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:105 0.000