Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 1 16 Jun 2025, 17:44

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 35:44.209 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:21.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.360
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 2.059
Then the computer boots Tails 1:15.879
And I see a disk failure message on the splash screen 2.976
After features/support/hooks.rb:330 0.836
After features/support/hooks.rb:100 0.016
1:18.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.352
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.281
Then the computer boots Tails 1:14.157
And I see a disk failure message on the splash screen 2.853
After features/support/hooks.rb:330 1.191
After features/support/hooks.rb:100 0.021
1:35.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.205
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.039
Then the computer boots Tails 1:13.544
And I see a disk failure message on the splash screen 20.358
After features/support/hooks.rb:330 0.807
After features/support/hooks.rb:100 0.015
Tags: @product @doc
1:40.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.247
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 36.037
When Tails detects disk read failures on the SquashFS 0.750
Then I see a disk failure message 3.045
Then I can open the hardware failure documentation from the disk failure message 1:0.129
After features/support/hooks.rb:330 3.874
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:31.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.267
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.530
When Tails detects disk read failures on the boot device 5.757
Then I see a disk failure message 5.475
Then I can open the hardware failure documentation from the disk failure message 57.637
After features/support/hooks.rb:330 5.970
After features/support/hooks.rb:100 0.000
Tags: @product @doc
32.074
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given a computer 0.390
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.522
When Tails detects disk read failures on the boot device with a target error 2.090
Then I see a disk failure message 10.070
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:31: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 6.550

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:50:53_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/1/artifact/build-artifacts/03:50:53_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/1/artifact/build-artifacts/03:50:53_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/1/artifact/build-artifacts/03:50:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
6:35.613
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 1:6.859
And I corrupt the boot device's GPT backup header 4.524
And I power off the computer 2.653
When I start the computer 2.746
Then the computer boots Tails 2:4.893
When I log in to a new session 3:13.935
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:330 5.865

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

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

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:57:35_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:57:35_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:100 0.055
Tags: @product
3:18.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.670
And I corrupt the boot device's GPT backup partition table 0.396
And I power off the computer 0.362
When I start the computer 10.852
Then the computer boots Tails 1:46.217
When I log in to a new session 41.492
And all notifications have disappeared 17.678
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.269
And Tails detected partitioning error partitioning-corruption 0.014
After features/support/hooks.rb:330 1.930
After features/support/hooks.rb:100 0.053
Tags: @product
4:40.293
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.085
Steps
Given a computer 0.483
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.065
And I write the Tails USB image to disk "temp" 1:19.449
When I start Tails from USB drive "temp" with network unplugged 3:19.243
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:54: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 forbids creating a persistent partition 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then I am recommended to reinstall Tails due to partitioning errors 0.000
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 0.000
And I am told that Persistent Storage cannot be created 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 13.525

SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 04:05:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/04:05:47_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/04:05:47_GPT_backup_corruption_without_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/04:05:47_GPT_backup_corruption_without_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/04:05:47_GPT_backup_corruption_without_a_persistent_partition.journal

After features/support/hooks.rb:100 0.223
Tags: @product
4:16.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.361
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.076
And I plug USB drive "temp" 1.096
And I write the Tails USB image to disk "temp" 1:19.111
When I start Tails from USB drive "temp" with network unplugged 2:48.491
Then Tails is running from USB drive "temp" 2.363
And the Greeter recommends reinstalling Tails due to partitioning errors 0.944
And the Greeter forbids starting Tails 0.614
And the Greeter forbids all settings but language 3.623
And Tails detected partitioning error guid-not-randomized 0.080
After features/support/hooks.rb:330 6.562
After features/support/hooks.rb:100 0.195
Tags: @product
5:16.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given a computer 1.124
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.840
And I plug USB drive "temp" 1.073
And I write the Tails USB image to disk "temp" 1:16.982
When I start Tails from USB drive "temp" with network unplugged 3:47.319
Then Tails is running from USB drive "temp" 4.554
And the Greeter recommends reinstalling Tails due to partitioning errors 0.874
And the Greeter forbids starting Tails 2.328
And the Greeter forbids all settings but language 1.143
And Tails detected partitioning error system-partition-not-resized 0.031
After features/support/hooks.rb:330 1.351
After features/support/hooks.rb:100 0.182
Tags: @product
3:37.285
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.233
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.216
And I plug USB drive "temp" 1.060
And I write the Tails USB image to disk "temp" 1:18.493
When I start Tails from USB drive "temp" with network unplugged 2:11.406
Then Tails is running from USB drive "temp" 3.822
And the Greeter recommends reinstalling Tails due to partitioning errors 0.640
And the Greeter forbids starting Tails 0.341
And the Greeter forbids all settings but language 1.043
And Tails detected partitioning error fs-not-resized 0.026
After features/support/hooks.rb:330 1.238
After features/support/hooks.rb:100 0.291