Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 8 05 May 2026, 00:37

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 65 5 25 0 0 95 7 5 12 22:4.345 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
26.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.740
Then the computer boots Tails 24.837
And I see a disk failure message on the splash screen 1.127
After features/support/hooks.rb:331 0.913
After features/support/hooks.rb:100 0.005
Tags: @product @broken_welcome_screen
27.742
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.718
Then the computer boots Tails 23.848
And I see a disk failure message on the splash screen 3.124
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.005
Tags: @product @broken_welcome_screen
26.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 0.823
Then the computer boots Tails 22.683
And I see a disk failure message on the splash screen 2.821
After features/support/hooks.rb:331 0.871
After features/support/hooks.rb:100 0.005
Tags: @product @doc
3:12.914
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given a computer 0.049
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 3:12.864
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:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542: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/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:331 5.402 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:40:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:40:06_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_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:40:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:40:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:40:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
3:12.652
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.042
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 3:12.609
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:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542: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/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:30: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 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:331 5.272 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:43:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:43:23_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_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:43:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:43:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:43:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
3:12.859
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given a computer 0.048
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 3:12.810
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:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542: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/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:331 5.480 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:46:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:46:42_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_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:46:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:46:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:46:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
3:12.562
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 3:12.562
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:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542: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/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:331 5.436 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 01:50:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:50:00_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_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:50:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:50:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:50:00_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
3:12.583
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 3:12.583
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:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542: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/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:46: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 partition table 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:331 5.251 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 01:53:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:53:18_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_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:53:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:53:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:53:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
1:35.685
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
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.007
And I plug USB drive "temp" 1.018
And I write the Tails USB image to disk "temp" 12.988
When I start Tails from USB drive "temp" with network unplugged 1:2.741
Then Tails is running from USB drive "temp" 0.547
And the Greeter forbids creating a persistent partition 0.046
When I log in to a new session 9.149
And all notifications have disappeared 6.647
Then I am recommended to reinstall Tails due to partitioning errors 0.118
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.175
And I am told that Persistent Storage cannot be created 1.191
And Tails detected partitioning error partitioning-corruption 0.004
After features/support/hooks.rb:331 0.754
After features/support/hooks.rb:100 0.121
Tags: @product
1:7.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
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.009
And I plug USB drive "temp" 1.015
And I write the Tails USB image to disk "temp" 13.325
When I start Tails from USB drive "temp" with network unplugged 52.659
Then Tails is running from USB drive "temp" 0.570
And the Greeter recommends reinstalling Tails due to partitioning errors 0.060
And the Greeter forbids starting Tails 0.032
And the Greeter forbids all settings but language 0.209
And Tails detected partitioning error guid-not-randomized 0.004
After features/support/hooks.rb:331 0.743
After features/support/hooks.rb:100 0.118
Tags: @product
59.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.127
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.007
And I plug USB drive "temp" 1.014
And I write the Tails USB image to disk "temp" 12.793
When I start Tails from USB drive "temp" with network unplugged 45.430
Then Tails is running from USB drive "temp" 0.235
And the Greeter recommends reinstalling Tails due to partitioning errors 0.043
And the Greeter forbids starting Tails 0.033
And the Greeter forbids all settings but language 0.157
And Tails detected partitioning error system-partition-not-resized 0.005
After features/support/hooks.rb:331 0.867
After features/support/hooks.rb:100 0.117
Tags: @product
56.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
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.007
And I plug USB drive "temp" 1.018
And I write the Tails USB image to disk "temp" 12.848
When I start Tails from USB drive "temp" with network unplugged 41.995
Then Tails is running from USB drive "temp" 0.248
And the Greeter recommends reinstalling Tails due to partitioning errors 0.043
And the Greeter forbids starting Tails 0.027
And the Greeter forbids all settings but language 0.167
And Tails detected partitioning error fs-not-resized 0.005
After features/support/hooks.rb:331 0.773
After features/support/hooks.rb:100 0.115