Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 101 24 Jun 2025, 21:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 46 3 38 0 0 87 4 3 7 22:56.203 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
3:32.999
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.267
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 58.338
When I start Tails from USB drive "old" with network unplugged 2:17.938
Then the boot device has safe access rights 4.559
And Tails is running from USB drive "old" 7.017
And there is no persistence partition on USB drive "old" 1.283
And process "udev-watchdog" is running 0.700
And udev-watchdog is monitoring the correct device 1.384
And I unplug USB drive "old" 0.390
After features/support/hooks.rb:335 3.692
After features/support/hooks.rb:105 0.008
Tags: @product
4:16.673
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.330
And I start Tails from USB drive "old" with network unplugged and I login 2:43.493
Then Tails is running from USB drive "old" 0.531
And I create a persistent partition 1:3.182
And I take note of which tps features are available 7.609
Then a Tails persistence partition exists on USB drive "old" 1.805
And I shutdown Tails and wait for the computer to power off 19.721
After features/support/hooks.rb:335 0.442
After features/support/hooks.rb:105 0.044
Tags: @product
6:3.662
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Given a computer 0.364
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:36.860
Then Tails is running from USB drive "old" 1.823
And all tps features are active 2.430
When I write some files expected to persist 2.212
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.911
And all persistence configuration files have safe access rights 1.200
And all persistent directories from the old Tails version have safe access rights 12.887
And I take note of which tps features are available 0.778
And I shutdown Tails and wait for the computer to power off 6.890
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 57.302
After features/support/hooks.rb:335 0.349
After features/support/hooks.rb:105 0.006
Tags: @product
1:33.788
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.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.642
And I log in to a new session 38.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.906
And I plug USB drive "to_upgrade" 7.546
When I upgrade Tails to USB drive "to_upgrade" by cloning 23.394
cannot 
cannot find TailsClonerWindow.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/usb.rb:156:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:187:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'
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 7.981 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:21:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/02:21:27_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/101/artifact/build-artifacts/02:21:27_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/101/artifact/build-artifacts/02:21:27_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/101/artifact/build-artifacts/02:21:27_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:105 0.000
Tags: @product
5:0.501
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Given a computer 0.490
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:37.970
Then all tps features from the old Tails version are active 2.600
And Tails is running from USB drive "to_upgrade" 2.679
And the boot device has safe access rights 11.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.769
And all persistent directories from the old Tails version have safe access rights 3.660
After features/support/hooks.rb:335 5.758
After features/support/hooks.rb:105 0.118
Tags: @product @automatic_upgrade
1:21.851
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.194
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:21.851
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 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.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~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.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:335 6.780 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:28:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/02:28:06_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/02:28:06_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/101/artifact/build-artifacts/02:28:06_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/101/artifact/build-artifacts/02:28:06_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.000
Tags: @product @automatic_upgrade
1:6.725
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 47.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.724
And the signing key used by the Upgrader is outdated 1.126
But a current signing key is available on our website 0.016
When the network is plugged 1.438
And Tor is ready 14.360
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 12.019 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:29:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/02:29:24_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/101/artifact/build-artifacts/02:29:24_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/101/artifact/build-artifacts/02:29:24_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/101/artifact/build-artifacts/02:29:24_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:105 0.000