Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 3 17 Jun 2025, 23:50

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 81 4 10 0 0 95 8 4 12 33:8.534 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:16.259
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given a computer 0.588
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.185
Then the computer boots Tails 1:12.409
And I see a disk failure message on the splash screen 2.076
After features/support/hooks.rb:330 0.564
After features/support/hooks.rb:100 0.009
1:18.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.272
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.323
Then the computer boots Tails 1:1.324
And I see a disk failure message on the splash screen 15.577
After features/support/hooks.rb:330 0.914
After features/support/hooks.rb:100 0.011
1:5.365
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.262
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.169
Then the computer boots Tails 59.573
And I see a disk failure message on the splash screen 4.361
After features/support/hooks.rb:330 3.397
After features/support/hooks.rb:100 0.171
Tags: @product @doc
1:22.461
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.122
Steps
Given a computer 1.682
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:20.778
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:29: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 SquashFS 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:330 8.456

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 03:05:04)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:04_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_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:04_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:04_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:04_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
37.541
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.247
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.695
When Tails detects disk read failures on the boot device 3.576
Then I see a disk failure message 10.022
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:330 5.913

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:05:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:49_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_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:05:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:32.485
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.225
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:32.260
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:330 7.163

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:07:28_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_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:07:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:07:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:07:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
3:30.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 25.491
And I corrupt the boot device's GPT backup header 1.514
And I power off the computer 1.170
When I start the computer 5.242
Then the computer boots Tails 1:59.083
When I log in to a new session 34.120
And all notifications have disappeared 14.345
Then I am recommended to migrate to a new USB stick due to partitioning errors 8.755
And Tails detected partitioning error partitioning-corruption 0.380
After features/support/hooks.rb:330 2.118
After features/support/hooks.rb:100 0.022
Tags: @product
5:19.779
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 17.762
And I corrupt the boot device's GPT backup partition table 2.207
And I power off the computer 0.690
When I start the computer 1.461
Then the computer boots Tails 1:45.000
When I log in to a new session 3:12.657
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:330 6.961

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:16:28_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_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:16:28_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:16:28_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/3/artifact/build-artifacts/03:16:28_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal

After features/support/hooks.rb:100 0.009
Tags: @product
5:20.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.279
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.049
And I plug USB drive "temp" 1.066
And I write the Tails USB image to disk "temp" 1:13.606
When I start Tails from USB drive "temp" with network unplugged 3:4.454
Then Tails is running from USB drive "temp" 0.712
And the Greeter forbids creating a persistent partition 0.117
When I log in to a new session 38.973
And all notifications have disappeared 15.134
Then I am recommended to reinstall Tails due to partitioning errors 0.291
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.328
And I am told that Persistent Storage cannot be created 4.169
And Tails detected partitioning error partitioning-corruption 0.014
After features/support/hooks.rb:330 2.575
After features/support/hooks.rb:100 1.441
Tags: @product
4:27.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.175
Given a computer 2.570
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.111
And I plug USB drive "temp" 1.436
And I write the Tails USB image to disk "temp" 57.745
When I start Tails from USB drive "temp" with network unplugged 3:21.222
Then Tails is running from USB drive "temp" 2.766
And the Greeter recommends reinstalling Tails due to partitioning errors 0.552
And the Greeter forbids starting Tails 0.224
And the Greeter forbids all settings but language 1.128
And Tails detected partitioning error guid-not-randomized 0.063
After features/support/hooks.rb:330 1.519
After features/support/hooks.rb:100 0.228
Tags: @product
3:45.957
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.212
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.052
And I plug USB drive "temp" 1.058
And I write the Tails USB image to disk "temp" 1:0.593
When I start Tails from USB drive "temp" with network unplugged 2:42.651
Then Tails is running from USB drive "temp" 0.381
And the Greeter recommends reinstalling Tails due to partitioning errors 0.069
And the Greeter forbids starting Tails 0.079
And the Greeter forbids all settings but language 0.813
And Tails detected partitioning error system-partition-not-resized 0.045
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.358
Tags: @product
3:32.058
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.316
Given a computer 2.501
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.134
And I plug USB drive "temp" 1.244
And I write the Tails USB image to disk "temp" 1:8.036
When I start Tails from USB drive "temp" with network unplugged 2:17.378
Then Tails is running from USB drive "temp" 1.958
And the Greeter recommends reinstalling Tails due to partitioning errors 0.130
And the Greeter forbids starting Tails 0.195
And the Greeter forbids all settings but language 0.461
And Tails detected partitioning error fs-not-resized 0.015
After features/support/hooks.rb:330 0.645
After features/support/hooks.rb:100 0.278