Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 116 08 Jul 2025, 21:50

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 80 3 12 0 0 95 9 3 12 31:57.727 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:34.583
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.229
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.602
Then the computer boots Tails 1:13.987
And I see a disk failure message on the splash screen 18.763
After features/support/hooks.rb:335 1.116
After features/support/hooks.rb:105 0.013
Tags: @product @broken_welcome_screen
1:3.770
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.236
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.195
Then the computer boots Tails 59.932
And I see a disk failure message on the splash screen 2.405
After features/support/hooks.rb:335 1.137
After features/support/hooks.rb:105 0.017
Tags: @product @broken_welcome_screen
1:17.979
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.012
Given a computer 0.355
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 1.442
Then the computer boots Tails 1:14.273
And I see a disk failure message on the splash screen 1.908
After features/support/hooks.rb:335 1.105
After features/support/hooks.rb:105 0.009
Tags: @product @doc
34.905
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.295
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.499
When Tails detects disk read failures on the SquashFS 2.102
Then I see a disk failure message 10.007
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 7.087 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 03:20:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/116/artifact/build-artifacts/03:20:48_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/116/artifact/build-artifacts/03:20:48_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/116/artifact/build-artifacts/03:20:48_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/116/artifact/build-artifacts/03:20:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:105 0.000
Tags: @product @doc
1:33.384
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.185
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.750
When Tails detects disk read failures on the boot device 2.684
Then I see a disk failure message 9.322
Then I can open the hardware failure documentation from the disk failure message 1:0.441
After features/support/hooks.rb:335 4.118
After features/support/hooks.rb:105 0.000
Tags: @product @doc
2:23.155
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.301
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:14.003
When Tails detects disk read failures on the boot device with a target error 2.069
Then I see a disk failure message 1.542
Then I can open the hardware failure documentation from the disk failure message 1:5.239
After features/support/hooks.rb:335 8.085
After features/support/hooks.rb:105 0.000
Tags: @product
1:23.270
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.152
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:23.270
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\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/hardware_failure.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
features/hardware_failure.feature:34:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
And I corrupt the boot device's GPT backup header 0.000
And I power off the computer 0.000
When I start the computer 0.000
Then the computer boots Tails 0.000
When I log in to a new session 0.000
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 5.883 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:26:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/116/artifact/build-artifacts/03:26:28_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/116/artifact/build-artifacts/03:26:28_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/116/artifact/build-artifacts/03:26:28_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/116/artifact/build-artifacts/03:26:28_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:105 0.000
Tags: @product
5:35.266
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.025
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 20.668
And I corrupt the boot device's GPT backup partition table 0.410
And I power off the computer 0.340
When I start the computer 1.083
Then the computer boots Tails 1:59.729
When I log in to a new session 3:13.033
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/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 5.542 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:32:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/116/artifact/build-artifacts/03:32:09_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/116/artifact/build-artifacts/03:32:09_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/116/artifact/build-artifacts/03:32:09_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/116/artifact/build-artifacts/03:32:09_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:105 0.019
Tags: @product
5:10.443
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.012
Given a computer 0.291
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.061
And I write the Tails USB image to disk "temp" 1:12.305
When I start Tails from USB drive "temp" with network unplugged 2:55.801
Then Tails is running from USB drive "temp" 4.248
And the Greeter forbids creating a persistent partition 0.140
When I log in to a new session 26.740
And all notifications have disappeared 17.367
Then I am recommended to reinstall Tails due to partitioning errors 0.452
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.470
And I am told that Persistent Storage cannot be created 9.991
And Tails detected partitioning error partitioning-corruption 0.520
After features/support/hooks.rb:335 4.073
After features/support/hooks.rb:105 0.263
Tags: @product
3:58.933
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given a computer 0.309
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.054
And I plug USB drive "temp" 1.073
And I write the Tails USB image to disk "temp" 1:2.713
When I start Tails from USB drive "temp" with network unplugged 2:49.560
Then Tails is running from USB drive "temp" 4.167
And the Greeter recommends reinstalling Tails due to partitioning errors 0.259
And the Greeter forbids starting Tails 0.167
And the Greeter forbids all settings but language 0.597
And Tails detected partitioning error guid-not-randomized 0.029
After features/support/hooks.rb:335 0.952
After features/support/hooks.rb:105 0.136
Tags: @product
3:43.733
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given a computer 0.193
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.046
And I plug USB drive "temp" 1.055
And I write the Tails USB image to disk "temp" 1:0.417
When I start Tails from USB drive "temp" with network unplugged 2:40.579
Then Tails is running from USB drive "temp" 0.800
And the Greeter recommends reinstalling Tails due to partitioning errors 0.093
And the Greeter forbids starting Tails 0.091
And the Greeter forbids all settings but language 0.439
And Tails detected partitioning error system-partition-not-resized 0.016
After features/support/hooks.rb:335 1.171
After features/support/hooks.rb:105 0.164
Tags: @product
3:38.302
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.256
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.046
And I plug USB drive "temp" 1.049
And I write the Tails USB image to disk "temp" 59.859
When I start Tails from USB drive "temp" with network unplugged 2:35.383
Then Tails is running from USB drive "temp" 0.925
And the Greeter recommends reinstalling Tails due to partitioning errors 0.097
And the Greeter forbids starting Tails 0.086
And the Greeter forbids all settings but language 0.561
And Tails detected partitioning error fs-not-resized 0.036
After features/support/hooks.rb:335 0.910
After features/support/hooks.rb:105 0.230