Project Number Date
test_Tails_ISO_21548-flatpak-install 14 22 May 2026, 14:43

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 83 3 9 0 0 95 9 3 12 10:27.017 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
29.769
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.065
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.751
Then the computer boots Tails 27.506
And I see a disk failure message on the splash screen 1.446
After features/support/hooks.rb:335 1.038
After features/support/hooks.rb:104 0.009
Tags: @product @broken_welcome_screen
29.323
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.109
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.882
Then the computer boots Tails 26.973
And I see a disk failure message on the splash screen 1.356
After features/support/hooks.rb:335 0.899
After features/support/hooks.rb:104 0.008
Tags: @product @broken_welcome_screen
27.694
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.091
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.777
Then the computer boots Tails 25.308
And I see a disk failure message on the splash screen 1.517
After features/support/hooks.rb:335 0.600
After features/support/hooks.rb:104 0.019
Tags: @product @doc
34.900
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Steps
Given a computer 0.089
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 34.810
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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: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:335 5.171 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:14:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:14: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_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
35.591
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Steps
Given a computer 0.249
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 35.342
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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: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:335 4.842 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:15:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_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_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
33.894
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Steps
Given a computer 0.073
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 33.820
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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: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:335 4.918 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:15:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_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_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.803
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.092
And I corrupt the boot device's GPT backup header 0.188
And I power off the computer 0.260
When I start the computer 0.795
Then the computer boots Tails 39.733
When I log in to a new session 11.248
And all notifications have disappeared 7.245
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.232
And Tails detected partitioning error partitioning-corruption 0.006
After features/support/hooks.rb:335 0.950
After features/support/hooks.rb:104 0.008
Tags: @product
1:8.375
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 7.866
And I corrupt the boot device's GPT backup partition table 0.215
And I power off the computer 0.316
When I start the computer 0.815
Then the computer boots Tails 38.858
When I log in to a new session 13.326
And all notifications have disappeared 6.778
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.179
And Tails detected partitioning error partitioning-corruption 0.017
After features/support/hooks.rb:335 0.855
After features/support/hooks.rb:104 0.006
Tags: @product
1:34.357
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.075
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.015
And I plug USB drive "temp" 1.021
And I write the Tails USB image to disk "temp" 14.179
When I start Tails from USB drive "temp" with network unplugged 58.262
Then Tails is running from USB drive "temp" 0.607
And the Greeter forbids creating a persistent partition 0.055
When I log in to a new session 10.470
And all notifications have disappeared 7.080
Then I am recommended to reinstall Tails due to partitioning errors 0.122
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.227
And I am told that Persistent Storage cannot be created 1.231
And Tails detected partitioning error partitioning-corruption 0.005
After features/support/hooks.rb:335 1.406
After features/support/hooks.rb:104 0.117
Tags: @product
1:14.994
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.074
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.013
And I plug USB drive "temp" 1.019
And I write the Tails USB image to disk "temp" 14.501
When I start Tails from USB drive "temp" with network unplugged 58.374
Then Tails is running from USB drive "temp" 0.696
And the Greeter recommends reinstalling Tails due to partitioning errors 0.052
And the Greeter forbids starting Tails 0.048
And the Greeter forbids all settings but language 0.208
And Tails detected partitioning error guid-not-randomized 0.005
After features/support/hooks.rb:335 0.788
After features/support/hooks.rb:104 0.127
Tags: @product
1:4.863
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
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.014
And I plug USB drive "temp" 1.024
And I write the Tails USB image to disk "temp" 13.887
When I start Tails from USB drive "temp" with network unplugged 49.026
Then Tails is running from USB drive "temp" 0.564
And the Greeter recommends reinstalling Tails due to partitioning errors 0.046
And the Greeter forbids starting Tails 0.033
And the Greeter forbids all settings but language 0.186
And Tails detected partitioning error system-partition-not-resized 0.006
After features/support/hooks.rb:335 0.858
After features/support/hooks.rb:104 0.110
Tags: @product
1:5.448
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.061
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.028
And I plug USB drive "temp" 1.026
And I write the Tails USB image to disk "temp" 13.958
When I start Tails from USB drive "temp" with network unplugged 49.132
Then Tails is running from USB drive "temp" 0.719
And the Greeter recommends reinstalling Tails due to partitioning errors 0.066
And the Greeter forbids starting Tails 0.048
And the Greeter forbids all settings but language 0.399
And Tails detected partitioning error fs-not-resized 0.007
After features/support/hooks.rb:335 0.929
After features/support/hooks.rb:104 0.145