Project Number Date
test_Tails_ISO_devel 3906 15 Jul 2025, 16:07

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 82 4 9 0 0 95 8 4 12 32:23.413 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:37.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.377
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.868
Then the computer boots Tails 1:20.494
And I see a disk failure message on the splash screen 14.981
After features/support/hooks.rb:330 1.043
After features/support/hooks.rb:100 0.016
Tags: @product @broken_welcome_screen
2:20.265
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given a computer 0.264
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 2.462
Then the computer boots Tails 1:17.534
And I see a disk failure message on the splash screen 1:0.003
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:43:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:17:in `And I see a disk failure message on the splash screen'
features/hardware_failure.feature:13:in `And I see a disk failure message on the splash screen'
After features/support/hooks.rb:330 5.026 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 03:31:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:31:20_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:31:20_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:31:20_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:31:20_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal
After features/support/hooks.rb:100 0.012
Tags: @product @broken_welcome_screen
1:33.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.224
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 8.961
Then the computer boots Tails 1:6.335
And I see a disk failure message on the splash screen 17.889
After features/support/hooks.rb:330 0.920
After features/support/hooks.rb:100 0.012
Tags: @product @doc
2:21.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.274
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:9.348
When Tails detects disk read failures on the SquashFS 4.230
Then I see a disk failure message 6.062
Then I can open the hardware failure documentation from the disk failure message 1:1.863
After features/support/hooks.rb:330 4.115
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:27.879
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Steps
Given a computer 3.905
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.974
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\ 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.665 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:36:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:36:54_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_devel/3906/artifact/build-artifacts/03:36:54_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:36:54_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:36:54_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:15.409
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given a computer 0.481
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:14.927
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\ 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 6.601 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 03:38:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:38:16_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_devel/3906/artifact/build-artifacts/03:38:16_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:38:16_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:38:16_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
3:13.702
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 50.161
And I corrupt the boot device's GPT backup header 0.677
And I power off the computer 0.977
When I start the computer 1.306
Then the computer boots Tails 1:43.148
When I log in to a new session 25.161
And all notifications have disappeared 11.940
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.316
And Tails detected partitioning error partitioning-corruption 0.012
After features/support/hooks.rb:330 0.833
After features/support/hooks.rb:100 0.009
Tags: @product
5:17.017
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 16.239
And I corrupt the boot device's GPT backup partition table 1.889
And I power off the computer 1.206
When I start the computer 1.374
Then the computer boots Tails 1:46.785
When I log in to a new session 3:9.521
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:330 5.989 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:46:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:46:55_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_devel/3906/artifact/build-artifacts/03:46:55_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:46:55_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3906/artifact/build-artifacts/03:46:55_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.013
Tags: @product
4:48.944
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.423
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.081
And I plug USB drive "temp" 1.068
And I write the Tails USB image to disk "temp" 1:12.844
When I start Tails from USB drive "temp" with network unplugged 2:43.503
Then Tails is running from USB drive "temp" 0.354
And the Greeter forbids creating a persistent partition 0.097
When I log in to a new session 25.715
And all notifications have disappeared 15.673
Then I am recommended to reinstall Tails due to partitioning errors 0.246
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.518
And I am told that Persistent Storage cannot be created 7.013
And Tails detected partitioning error partitioning-corruption 0.402
After features/support/hooks.rb:330 3.404
After features/support/hooks.rb:100 0.282
Tags: @product
3:20.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Given a computer 0.507
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.094
And I plug USB drive "temp" 1.152
And I write the Tails USB image to disk "temp" 44.517
When I start Tails from USB drive "temp" with network unplugged 2:32.142
Then Tails is running from USB drive "temp" 1.064
And the Greeter recommends reinstalling Tails due to partitioning errors 0.115
And the Greeter forbids starting Tails 0.130
And the Greeter forbids all settings but language 1.034
And Tails detected partitioning error guid-not-randomized 0.029
After features/support/hooks.rb:330 1.851
After features/support/hooks.rb:100 0.229
Tags: @product
2:22.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.271
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.062
And I plug USB drive "temp" 1.065
And I write the Tails USB image to disk "temp" 34.139
When I start Tails from USB drive "temp" with network unplugged 1:46.225
Then Tails is running from USB drive "temp" 0.348
And the Greeter recommends reinstalling Tails due to partitioning errors 0.074
And the Greeter forbids starting Tails 0.067
And the Greeter forbids all settings but language 0.378
And Tails detected partitioning error system-partition-not-resized 0.012
After features/support/hooks.rb:330 0.631
After features/support/hooks.rb:100 0.140
Tags: @product
2:43.844
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.251
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.062
And I plug USB drive "temp" 1.064
And I write the Tails USB image to disk "temp" 35.224
When I start Tails from USB drive "temp" with network unplugged 2:5.517
Then Tails is running from USB drive "temp" 0.908
And the Greeter recommends reinstalling Tails due to partitioning errors 0.104
And the Greeter forbids starting Tails 0.121
And the Greeter forbids all settings but language 0.572
And Tails detected partitioning error fs-not-resized 0.017
After features/support/hooks.rb:330 0.802
After features/support/hooks.rb:100 0.207