Project Number Date
test_Tails_ISO_feature-arti 90 16 Jun 2025, 17:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 70 5 20 0 0 95 7 5 12 34:17.186 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:21.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.949
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.351
Then the computer boots Tails 1:15.493
And I see a disk failure message on the splash screen 3.401
After features/support/hooks.rb:330 0.721
After features/support/hooks.rb:100 0.014
Tags: @product @broken_welcome_screen
1:20.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.040
Then the computer boots Tails 1:14.624
And I see a disk failure message on the splash screen 5.024
After features/support/hooks.rb:330 4.996
After features/support/hooks.rb:100 0.238
Tags: @product @broken_welcome_screen
1:13.475
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.198
Given a computer 0.873
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 5.926
Then the computer boots Tails 1:2.515
And I see a disk failure message on the splash screen 4.159
After features/support/hooks.rb:330 0.646
After features/support/hooks.rb:100 0.010
Tags: @product @doc
1:30.188
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.205
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.983
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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 6.278 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 03:47:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:47:23_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_feature-arti/90/artifact/build-artifacts/03:47:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:47:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:47:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:15.787
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given a computer 0.312
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.474
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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: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:330 6.273 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:48:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:48:45_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_feature-arti/90/artifact/build-artifacts/03:48:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:48:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:48:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:30.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.004
When Tails detects disk read failures on the boot device with a target error 5.397
Then I see a disk failure message 6.411
Then I can open the hardware failure documentation from the disk failure message 54.998
After features/support/hooks.rb:330 7.846
After features/support/hooks.rb:100 0.000
Tags: @product
5:35.550
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 33.067
And I corrupt the boot device's GPT backup header 1.748
And I power off the computer 0.756
When I start the computer 1.943
Then the computer boots Tails 1:44.733
When I log in to a new session 3:13.300
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:577:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:533: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.921 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:56:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:56:06_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_feature-arti/90/artifact/build-artifacts/03:56:06_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:56:06_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/03:56:06_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.012
Tags: @product
5:34.993
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.459
And I corrupt the boot device's GPT backup partition table 1.020
And I power off the computer 7.341
When I start the computer 4.660
Then the computer boots Tails 1:45.307
When I log in to a new session 3:15.203
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:577:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:533: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.226 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 04:01:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/04:01:47_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_feature-arti/90/artifact/build-artifacts/04:01:47_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/04:01:47_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/04:01:47_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.960
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.194
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.058
And I write the Tails USB image to disk "temp" 1:34.922
When I start Tails from USB drive "temp" with network unplugged 29.735
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/screen.rb:320:in `sleep'
./features/support/helpers/screen.rb:320:in `press'
./features/support/helpers/screen.rb:329:in `block (2 levels) in type'
./features/support/helpers/screen.rb:328:in `each_char'
./features/support/helpers/screen.rb:328:in `block in type'
./features/support/helpers/screen.rb:325:in `each'
./features/support/helpers/screen.rb:325:in `type'
./features/step_definitions/common_steps.rb:457:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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 12.705 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 04:04:02)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/04:04:02_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/04:04:02_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/90/artifact/build-artifacts/04:04:02_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.125
Tags: @product
4:37.533
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.200
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.044
And I plug USB drive "temp" 1.056
And I write the Tails USB image to disk "temp" 1:32.466
When I start Tails from USB drive "temp" with network unplugged 3:2.405
Then Tails is running from USB drive "temp" 0.494
And the Greeter recommends reinstalling Tails due to partitioning errors 0.111
And the Greeter forbids starting Tails 0.085
And the Greeter forbids all settings but language 0.653
And Tails detected partitioning error guid-not-randomized 0.015
After features/support/hooks.rb:330 1.326
After features/support/hooks.rb:100 0.149
Tags: @product
4:14.229
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.286
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.087
And I plug USB drive "temp" 1.075
And I write the Tails USB image to disk "temp" 1:18.124
When I start Tails from USB drive "temp" with network unplugged 2:44.362
Then Tails is running from USB drive "temp" 7.723
And the Greeter recommends reinstalling Tails due to partitioning errors 1.190
And the Greeter forbids starting Tails 0.206
And the Greeter forbids all settings but language 1.149
And Tails detected partitioning error system-partition-not-resized 0.022
After features/support/hooks.rb:330 1.284
After features/support/hooks.rb:100 0.171
Tags: @product
3:57.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.249
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.064
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 1:12.135
When I start Tails from USB drive "temp" with network unplugged 2:32.668
Then Tails is running from USB drive "temp" 5.936
And the Greeter recommends reinstalling Tails due to partitioning errors 0.762
And the Greeter forbids starting Tails 1.008
And the Greeter forbids all settings but language 3.381
And Tails detected partitioning error fs-not-resized 0.057
After features/support/hooks.rb:330 1.901
After features/support/hooks.rb:100 0.213