Project Number Date
test_Tails_ISO_stable 5768 15 Jul 2025, 18:50

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 82 2 11 0 0 95 10 2 12 33:45.921 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:22.830
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.363
Then the computer boots Tails 1:0.296
And I see a disk failure message on the splash screen 20.934
After features/support/hooks.rb:330 0.795
After features/support/hooks.rb:100 0.027
1:19.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given a computer 0.256
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.195
Then the computer boots Tails 1:15.678
And I see a disk failure message on the splash screen 2.253
After features/support/hooks.rb:330 0.994
After features/support/hooks.rb:100 0.017
1:15.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.437
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.201
Then the computer boots Tails 1:12.126
And I see a disk failure message on the splash screen 2.181
After features/support/hooks.rb:330 0.843
After features/support/hooks.rb:100 0.055
Tags: @product @doc
1:44.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.332
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 47.204
When Tails detects disk read failures on the SquashFS 5.594
Then I see a disk failure message 4.001
Then I can open the hardware failure documentation from the disk failure message 46.983
After features/support/hooks.rb:330 8.810
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:24.243
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 0.787
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.296
When Tails detects disk read failures on the boot device 4.313
Then I see a disk failure message 3.770
Then I can open the hardware failure documentation from the disk failure message 1:0.075
After features/support/hooks.rb:330 3.759
After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:40.200
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.294
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.428
When Tails detects disk read failures on the boot device with a target error 7.779
Then I see a disk failure message 5.681
Then I can open the hardware failure documentation from the disk failure message 1:3.016
After features/support/hooks.rb:330 4.799
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.560
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.429
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:27.560
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\ 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:330 5.516

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5768/artifact/build-artifacts/03:35:41_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_stable/5768/artifact/build-artifacts/03:35:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5768/artifact/build-artifacts/03:35:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5768/artifact/build-artifacts/03:35:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
6:36.147
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
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:7.714
And I corrupt the boot device's GPT backup partition table 3.369
And I power off the computer 0.854
When I start the computer 4.768
Then the computer boots Tails 2:6.618
When I log in to a new session 3:12.822
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.880

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:42:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5768/artifact/build-artifacts/03:42:22_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_stable/5768/artifact/build-artifacts/03:42:22_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5768/artifact/build-artifacts/03:42:22_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5768/artifact/build-artifacts/03:42:22_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal

After features/support/hooks.rb:100 0.047
Tags: @product
5:30.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Given a computer 0.342
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.066
And I plug USB drive "temp" 1.084
And I write the Tails USB image to disk "temp" 1:18.881
When I start Tails from USB drive "temp" with network unplugged 3:0.535
Then Tails is running from USB drive "temp" 0.481
And the Greeter forbids creating a persistent partition 0.089
When I log in to a new session 39.745
And all notifications have disappeared 17.983
Then I am recommended to reinstall Tails due to partitioning errors 0.512
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.440
And I am told that Persistent Storage cannot be created 9.012
And Tails detected partitioning error partitioning-corruption 0.375
After features/support/hooks.rb:330 3.356
After features/support/hooks.rb:100 0.211
Tags: @product
4:2.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.322
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.054
And I plug USB drive "temp" 1.053
And I write the Tails USB image to disk "temp" 1:2.177
When I start Tails from USB drive "temp" with network unplugged 2:58.191
Then Tails is running from USB drive "temp" 0.385
And the Greeter recommends reinstalling Tails due to partitioning errors 0.076
And the Greeter forbids starting Tails 0.089
And the Greeter forbids all settings but language 0.353
And Tails detected partitioning error guid-not-randomized 0.015
After features/support/hooks.rb:330 0.919
After features/support/hooks.rb:100 0.172
Tags: @product
3:36.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.448
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.094
And I plug USB drive "temp" 1.110
And I write the Tails USB image to disk "temp" 1:0.882
When I start Tails from USB drive "temp" with network unplugged 2:29.486
Then Tails is running from USB drive "temp" 2.341
And the Greeter recommends reinstalling Tails due to partitioning errors 0.387
And the Greeter forbids starting Tails 0.303
And the Greeter forbids all settings but language 1.292
And Tails detected partitioning error system-partition-not-resized 0.073
After features/support/hooks.rb:330 1.482
After features/support/hooks.rb:100 0.255
Tags: @product
3:45.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.268
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.044
And I plug USB drive "temp" 1.069
And I write the Tails USB image to disk "temp" 1:0.116
When I start Tails from USB drive "temp" with network unplugged 2:43.184
Then Tails is running from USB drive "temp" 0.604
And the Greeter recommends reinstalling Tails due to partitioning errors 0.089
And the Greeter forbids starting Tails 0.069
And the Greeter forbids all settings but language 0.339
And Tails detected partitioning error fs-not-resized 0.013
After features/support/hooks.rb:330 3.348
After features/support/hooks.rb:100 0.964