Project Number Date
test_Tails_ISO_21548-flatpak-install 13 22 May 2026, 13:38

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:46.326 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
26.952
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.085
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.811
Then the computer boots Tails 24.503
And I see a disk failure message on the splash screen 1.552
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:104 0.008
Tags: @product @broken_welcome_screen
29.308
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.073
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.875
Then the computer boots Tails 27.149
And I see a disk failure message on the splash screen 1.208
After features/support/hooks.rb:335 0.888
After features/support/hooks.rb:104 0.008
Tags: @product @broken_welcome_screen
29.152
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.062
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.776
Then the computer boots Tails 26.718
And I see a disk failure message on the splash screen 1.595
After features/support/hooks.rb:335 0.751
After features/support/hooks.rb:104 0.008
Tags: @product @doc
36.275
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.061
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 36.214
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.388 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:14:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:14:28_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/13/artifact/build-artifacts/01:14:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:14:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:14:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
33.948
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Steps
Given a computer 0.079
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 33.868
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.929 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:15:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:15:07_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/13/artifact/build-artifacts/01:15:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:15:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:15:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
34.108
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.078
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 34.030
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.964 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:15:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:15:46_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/13/artifact/build-artifacts/01:15:46_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:15:46_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/13/artifact/build-artifacts/01:15:46_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.621
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.048
And I corrupt the boot device's GPT backup header 0.208
And I power off the computer 0.265
When I start the computer 0.823
Then the computer boots Tails 40.514
When I log in to a new session 12.471
And all notifications have disappeared 7.128
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.155
And Tails detected partitioning error partitioning-corruption 0.005
After features/support/hooks.rb:335 0.662
After features/support/hooks.rb:104 0.006
Tags: @product
1:8.836
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 7.934
And I corrupt the boot device's GPT backup partition table 0.306
And I power off the computer 0.296
When I start the computer 0.841
Then the computer boots Tails 39.686
When I log in to a new session 12.551
And all notifications have disappeared 7.062
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.151
And Tails detected partitioning error partitioning-corruption 0.005
After features/support/hooks.rb:335 0.912
After features/support/hooks.rb:104 0.007
Tags: @product
1:52.086
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.085
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.030
And I plug USB drive "temp" 1.031
And I write the Tails USB image to disk "temp" 14.105
When I start Tails from USB drive "temp" with network unplugged 1:15.395
Then Tails is running from USB drive "temp" 0.719
And the Greeter forbids creating a persistent partition 0.048
When I log in to a new session 11.076
And all notifications have disappeared 7.012
Then I am recommended to reinstall Tails due to partitioning errors 0.120
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.182
And I am told that Persistent Storage cannot be created 1.271
And Tails detected partitioning error partitioning-corruption 0.005
After features/support/hooks.rb:335 1.238
After features/support/hooks.rb:104 0.115
Tags: @product
1:7.127
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.070
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.008
And I plug USB drive "temp" 1.021
And I write the Tails USB image to disk "temp" 14.318
When I start Tails from USB drive "temp" with network unplugged 50.600
Then Tails is running from USB drive "temp" 0.798
And the Greeter recommends reinstalling Tails due to partitioning errors 0.060
And the Greeter forbids starting Tails 0.056
And the Greeter forbids all settings but language 0.187
And Tails detected partitioning error guid-not-randomized 0.004
After features/support/hooks.rb:335 0.649
After features/support/hooks.rb:104 0.174
Tags: @product
1:8.294
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Given a computer 0.123
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.012
And I plug USB drive "temp" 1.021
And I write the Tails USB image to disk "temp" 14.645
When I start Tails from USB drive "temp" with network unplugged 51.709
Then Tails is running from USB drive "temp" 0.518
And the Greeter recommends reinstalling Tails due to partitioning errors 0.047
And the Greeter forbids starting Tails 0.033
And the Greeter forbids all settings but language 0.172
And Tails detected partitioning error system-partition-not-resized 0.009
After features/support/hooks.rb:335 0.925
After features/support/hooks.rb:104 0.114
Tags: @product
1:10.613
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.060
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.008
And I plug USB drive "temp" 1.018
And I write the Tails USB image to disk "temp" 14.632
When I start Tails from USB drive "temp" with network unplugged 53.852
Then Tails is running from USB drive "temp" 0.652
And the Greeter recommends reinstalling Tails due to partitioning errors 0.090
And the Greeter forbids starting Tails 0.035
And the Greeter forbids all settings but language 0.257
And Tails detected partitioning error fs-not-resized 0.005
After features/support/hooks.rb:335 0.674
After features/support/hooks.rb:104 0.118