Project Number Date
test_Tails_ISO_stable 5732 24 Jun 2025, 12:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 87 3 5 0 0 95 9 3 12 31:17.291 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:17.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.215
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 11.221
Then the computer boots Tails 1:3.066
And I see a disk failure message on the splash screen 3.025
After features/support/hooks.rb:330 1.403
After features/support/hooks.rb:100 0.042
Tags: @product @broken_welcome_screen
1:18.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.328
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.803
Then the computer boots Tails 1:14.597
And I see a disk failure message on the splash screen 1.926
After features/support/hooks.rb:330 0.864
After features/support/hooks.rb:100 0.014
Tags: @product @broken_welcome_screen
1:19.053
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.218
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.020
Then the computer boots Tails 1:15.236
And I see a disk failure message on the splash screen 2.578
After features/support/hooks.rb:330 0.781
After features/support/hooks.rb:100 0.031
Tags: @product @doc
32.786
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.067
Steps
Given a computer 0.352
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.980
When Tails detects disk read failures on the SquashFS 1.108
Then I see a disk failure message 10.346
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:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29: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.861 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 03:20:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:20:26_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_stable/5732/artifact/build-artifacts/03:20:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:20:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:20:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
32.752
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.182
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.046
When Tails detects disk read failures on the boot device 0.502
Then I see a disk failure message 10.021
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: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 6.112 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:21:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:21:05_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_stable/5732/artifact/build-artifacts/03:21:05_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:21:05_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:21:05_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:11.481
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.042
Steps
Given a computer 0.245
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:11.236
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 7.415 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 03:22:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:22:23_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_stable/5732/artifact/build-artifacts/03:22:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:22:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5732/artifact/build-artifacts/03:22:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
3:32.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 22.974
And I corrupt the boot device's GPT backup header 0.461
And I power off the computer 0.509
When I start the computer 1.134
Then the computer boots Tails 2:10.923
When I log in to a new session 37.920
And all notifications have disappeared 11.859
Then I am recommended to migrate to a new USB stick due to partitioning errors 6.501
And Tails detected partitioning error partitioning-corruption 0.323
After features/support/hooks.rb:330 4.573
After features/support/hooks.rb:100 0.051
Tags: @product
3:43.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 50.821
And I corrupt the boot device's GPT backup partition table 5.857
And I power off the computer 1.937
When I start the computer 1.405
Then the computer boots Tails 1:49.090
When I log in to a new session 35.999
And all notifications have disappeared 17.911
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.586
And Tails detected partitioning error partitioning-corruption 0.024
After features/support/hooks.rb:330 1.780
After features/support/hooks.rb:100 0.012
Tags: @product
4:52.768
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
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.056
And I plug USB drive "temp" 1.058
And I write the Tails USB image to disk "temp" 1:13.313
When I start Tails from USB drive "temp" with network unplugged 2:38.750
Then Tails is running from USB drive "temp" 0.521
And the Greeter forbids creating a persistent partition 0.083
When I log in to a new session 26.977
And all notifications have disappeared 15.715
Then I am recommended to reinstall Tails due to partitioning errors 0.683
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.344
And I am told that Persistent Storage cannot be created 13.805
And Tails detected partitioning error partitioning-corruption 0.238
After features/support/hooks.rb:330 1.559
After features/support/hooks.rb:100 0.136
Tags: @product
4:39.321
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.259
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.057
And I plug USB drive "temp" 1.068
And I write the Tails USB image to disk "temp" 1:5.196
When I start Tails from USB drive "temp" with network unplugged 3:22.072
Then Tails is running from USB drive "temp" 6.678
And the Greeter recommends reinstalling Tails due to partitioning errors 2.310
And the Greeter forbids starting Tails 0.623
And the Greeter forbids all settings but language 1.018
And Tails detected partitioning error guid-not-randomized 0.035
After features/support/hooks.rb:330 1.074
After features/support/hooks.rb:100 0.144
Tags: @product
4:21.094
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
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.044
And I plug USB drive "temp" 1.058
And I write the Tails USB image to disk "temp" 1:1.088
When I start Tails from USB drive "temp" with network unplugged 3:17.066
Then Tails is running from USB drive "temp" 0.735
And the Greeter recommends reinstalling Tails due to partitioning errors 0.087
And the Greeter forbids starting Tails 0.085
And the Greeter forbids all settings but language 0.683
And Tails detected partitioning error system-partition-not-resized 0.021
After features/support/hooks.rb:330 1.236
After features/support/hooks.rb:100 0.371
Tags: @product
3:55.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.041
Given a computer 0.470
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.138
And I plug USB drive "temp" 1.080
And I write the Tails USB image to disk "temp" 59.062
When I start Tails from USB drive "temp" with network unplugged 2:51.148
Then Tails is running from USB drive "temp" 2.618
And the Greeter recommends reinstalling Tails due to partitioning errors 0.192
And the Greeter forbids starting Tails 0.153
And the Greeter forbids all settings but language 0.712
And Tails detected partitioning error fs-not-resized 0.027
After features/support/hooks.rb:330 1.190
After features/support/hooks.rb:100 0.183