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
Hardware failures 87 3 5 0 0 95 9 3 12 30:18.050 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
Tags: @product @broken_welcome_screen
1:20.258
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.316
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 2.086
Then the computer boots Tails 1:14.778
And I see a disk failure message on the splash screen 3.078
After features/support/hooks.rb:335 0.981
After features/support/hooks.rb:105 0.014
Tags: @product @broken_welcome_screen
1:20.325
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.352
And boot device is damaged in a way that some read operations fail 0.002
When I start the computer 1.239
Then the computer boots Tails 1:15.261
And I see a disk failure message on the splash screen 3.470
After features/support/hooks.rb:335 1.028
After features/support/hooks.rb:105 0.011
Tags: @product @broken_welcome_screen
1:17.074
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.220
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 6.242
Then the computer boots Tails 1:8.082
And I see a disk failure message on the splash screen 2.530
After features/support/hooks.rb:335 1.180
After features/support/hooks.rb:105 0.009
Tags: @product @doc
31.710
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Steps
Given a computer 0.208
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.719
When Tails detects disk read failures on the SquashFS 0.776
Then I see a disk failure message 10.005
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29:in `Then I see a disk failure message'
features/hardware_failure.feature:25:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:335 6.372 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 03:30:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:30:19_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.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/03:30:19_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:30:19_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:30:19_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:105 0.000
Tags: @product @doc
33.106
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Steps
Given a computer 0.428
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.755
When Tails detects disk read failures on the boot device 0.911
Then I see a disk failure message 10.011
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:30:in `Then I see a disk failure message'
features/hardware_failure.feature:25:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:335 6.468 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:30:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:30:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.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/03:30:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:30:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:30:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:105 0.000
Tags: @product @doc
1:15.757
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Steps
Given a computer 0.341
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.416
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/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 7.146 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 03:32:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/118/artifact/build-artifacts/03:32:21_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/118/artifact/build-artifacts/03:32:21_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/118/artifact/build-artifacts/03:32:21_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/118/artifact/build-artifacts/03:32:21_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:105 0.000
Tags: @product
3:24.720
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.012
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 23.181
And I corrupt the boot device's GPT backup header 3.131
And I power off the computer 0.995
When I start the computer 5.952
Then the computer boots Tails 1:54.139
When I log in to a new session 44.792
And all notifications have disappeared 9.335
Then I am recommended to migrate to a new USB stick due to partitioning errors 2.782
And Tails detected partitioning error partitioning-corruption 0.409
After features/support/hooks.rb:335 5.845
After features/support/hooks.rb:105 0.035
Tags: @product
3:44.888
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.027
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 15.989
And I corrupt the boot device's GPT backup partition table 1.438
And I power off the computer 0.928
When I start the computer 5.325
Then the computer boots Tails 2:18.297
When I log in to a new session 48.370
And all notifications have disappeared 14.317
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.209
And Tails detected partitioning error partitioning-corruption 0.012
After features/support/hooks.rb:335 0.964
After features/support/hooks.rb:105 0.010
Tags: @product
5:20.816
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.253
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.050
And I plug USB drive "temp" 1.076
And I write the Tails USB image to disk "temp" 1:15.293
When I start Tails from USB drive "temp" with network unplugged 3:2.059
Then Tails is running from USB drive "temp" 0.368
And the Greeter forbids creating a persistent partition 0.089
When I log in to a new session 40.969
And all notifications have disappeared 7.477
Then I am recommended to reinstall Tails due to partitioning errors 4.008
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 4.906
And I am told that Persistent Storage cannot be created 4.244
And Tails detected partitioning error partitioning-corruption 0.017
After features/support/hooks.rb:335 2.178
After features/support/hooks.rb:105 0.120
Tags: @product
4:18.678
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.266
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.049
And I plug USB drive "temp" 1.073
And I write the Tails USB image to disk "temp" 1:13.757
When I start Tails from USB drive "temp" with network unplugged 3:2.328
Then Tails is running from USB drive "temp" 0.409
And the Greeter recommends reinstalling Tails due to partitioning errors 0.105
And the Greeter forbids starting Tails 0.109
And the Greeter forbids all settings but language 0.565
And Tails detected partitioning error guid-not-randomized 0.013
After features/support/hooks.rb:335 1.089
After features/support/hooks.rb:105 0.178
Tags: @product
3:44.487
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.213
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.067
And I plug USB drive "temp" 1.061
And I write the Tails USB image to disk "temp" 1:5.853
When I start Tails from USB drive "temp" with network unplugged 2:33.273
Then Tails is running from USB drive "temp" 0.406
And the Greeter recommends reinstalling Tails due to partitioning errors 0.081
And the Greeter forbids starting Tails 0.079
And the Greeter forbids all settings but language 2.851
And Tails detected partitioning error system-partition-not-resized 0.598
After features/support/hooks.rb:335 6.384
After features/support/hooks.rb:105 0.381
Tags: @product
3:26.224
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.019
Given a computer 0.599
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.114
And I plug USB drive "temp" 1.349
And I write the Tails USB image to disk "temp" 1:1.176
When I start Tails from USB drive "temp" with network unplugged 2:21.833
Then Tails is running from USB drive "temp" 0.547
And the Greeter recommends reinstalling Tails due to partitioning errors 0.078
And the Greeter forbids starting Tails 0.075
And the Greeter forbids all settings but language 0.401
And Tails detected partitioning error fs-not-resized 0.047
After features/support/hooks.rb:335 1.285
After features/support/hooks.rb:105 0.192