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
Hardware failures 77 4 14 0 0 95 8 4 12 38:0.161 Failed
Tags: @product
Feature Hardware failures
In order to update my failing hardware before I lose data As a Tails user I want to be warned about hardware failures
1:23.937
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.027
Given a computer 0.666
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.527
Then the computer boots Tails 1:17.798
And I see a disk failure message on the splash screen 3.945
After features/support/hooks.rb:335 3.281
After features/support/hooks.rb:105 0.304
1:30.005
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.236
Given a computer 2.209
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 6.092
Then the computer boots Tails 1:3.759
And I see a disk failure message on the splash screen 17.943
After features/support/hooks.rb:335 0.899
After features/support/hooks.rb:105 0.015
1:20.160
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Given a computer 0.278
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 2.614
Then the computer boots Tails 1:14.399
And I see a disk failure message on the splash screen 2.867
After features/support/hooks.rb:335 0.969
After features/support/hooks.rb:105 0.039
Tags: @product @doc
1:38.302
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.024
Given a computer 0.526
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.261
When Tails detects disk read failures on the SquashFS 4.553
Then I see a disk failure message 5.290
Then I can open the hardware failure documentation from the disk failure message 1:0.670
After features/support/hooks.rb:335 3.874
After features/support/hooks.rb:105 0.000
Tags: @product @doc
1:55.235
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.073
Given a computer 0.469
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.958
When Tails detects disk read failures on the boot device 7.157
Then I see a disk failure message 3.803
Then I can open the hardware failure documentation from the disk failure message 1:19.846
After features/support/hooks.rb:335 4.350
After features/support/hooks.rb:105 0.000
Tags: @product @doc
1:54.968
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.028
Steps
Given a computer 0.766
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:54.201
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/hardware_failure.feature:31:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device with a target error 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:335 14.840

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 03:33:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:33:22_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.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/03:33:22_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:33:22_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:33:22_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal

After features/support/hooks.rb:105 0.000
Tags: @product
6:23.226
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.045
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 34.180
And I corrupt the boot device's GPT backup header 8.286
And I power off the computer 0.798
When I start the computer 2.572
Then the computer boots Tails 2:23.940
When I log in to a new session 3:13.449
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/hardware_failure.feature:45:in `When I log in to a new session'
features/hardware_failure.feature:39:in `When I log in to a new session'
And all notifications have disappeared 0.000
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:335 6.142

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:40:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:40:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.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/03:40:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:40:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:40:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:105 0.012
Tags: @product
5:53.356
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 23.079
And I corrupt the boot device's GPT backup partition table 2.598
And I power off the computer 3.124
When I start the computer 4.485
Then the computer boots Tails 2:6.241
When I log in to a new session 3:13.826
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/hardware_failure.feature:46:in `When I log in to a new session'
features/hardware_failure.feature:39:in `When I log in to a new session'
And all notifications have disappeared 0.000
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:335 6.912

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:46:00)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:46:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.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/03:46:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:46:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:46:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal

After features/support/hooks.rb:105 0.028
Tags: @product
4:59.402
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.036
Given a computer 0.211
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.055
And I plug USB drive "temp" 1.062
And I write the Tails USB image to disk "temp" 1:17.027
When I start Tails from USB drive "temp" with network unplugged 2:46.746
Then Tails is running from USB drive "temp" 1.926
And the Greeter forbids creating a persistent partition 0.490
When I log in to a new session 29.534
And all notifications have disappeared 16.647
Then I am recommended to reinstall Tails due to partitioning errors 0.296
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.282
And I am told that Persistent Storage cannot be created 4.105
And Tails detected partitioning error partitioning-corruption 0.015
After features/support/hooks.rb:335 1.685
After features/support/hooks.rb:105 0.711
Tags: @product
3:51.308
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.096
Steps
Given a computer 1.190
And I set Tails to boot with options "test_partitioning_errors=guid" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.288
And I plug USB drive "temp" 1.209
And I write the Tails USB image to disk "temp" 1:7.862
When I start Tails from USB drive "temp" with network unplugged 2:40.758
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/hardware_failure.feature:80:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error guid-not-randomized 0.000
After features/support/hooks.rb:335 7.237

SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#1)' (at time 03:55:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:55:01_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.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/03:55:01_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:55:01_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/103/artifact/build-artifacts/03:55:01_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:105 0.193
Tags: @product
4:18.826
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given a computer 1.793
And I set Tails to boot with options "test_partitioning_errors=part_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.983
And I plug USB drive "temp" 2.501
And I write the Tails USB image to disk "temp" 1:10.161
When I start Tails from USB drive "temp" with network unplugged 3:1.888
Then Tails is running from USB drive "temp" 0.761
And the Greeter recommends reinstalling Tails due to partitioning errors 0.156
And the Greeter forbids starting Tails 0.137
And the Greeter forbids all settings but language 0.427
And Tails detected partitioning error system-partition-not-resized 0.013
After features/support/hooks.rb:335 1.240
After features/support/hooks.rb:105 0.704
Tags: @product
2:51.430
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.116
Given a computer 5.353
And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.137
And I plug USB drive "temp" 1.149
And I write the Tails USB image to disk "temp" 44.422
When I start Tails from USB drive "temp" with network unplugged 1:59.491
Then Tails is running from USB drive "temp" 0.377
And the Greeter recommends reinstalling Tails due to partitioning errors 0.082
And the Greeter forbids starting Tails 0.072
And the Greeter forbids all settings but language 0.328
And Tails detected partitioning error fs-not-resized 0.015
After features/support/hooks.rb:335 0.749
After features/support/hooks.rb:105 0.188