Project Number Date
test_Tails_ISO_21548-flatpak-install 12 22 May 2026, 12:05

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:15.555 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
30.461
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.071
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.898
Then the computer boots Tails 26.491
And I see a disk failure message on the splash screen 3.000
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:104 0.006
Tags: @product @broken_welcome_screen
27.251
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.063
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.762
Then the computer boots Tails 25.091
And I see a disk failure message on the splash screen 1.334
After features/support/hooks.rb:335 0.957
After features/support/hooks.rb:104 0.007
Tags: @product @broken_welcome_screen
30.862
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
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.878
Then the computer boots Tails 26.504
And I see a disk failure message on the splash screen 3.419
After features/support/hooks.rb:335 0.868
After features/support/hooks.rb:104 0.009
Tags: @product @doc
33.009
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.069
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.940
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 4.942 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:12:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:12:14_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/12/artifact/build-artifacts/01:12:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:12:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:12:14_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
32.084
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Steps
Given a computer 0.086
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.998
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.823 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:12:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:12:51_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/12/artifact/build-artifacts/01:12:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:12:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:12:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
32.599
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Steps
Given a computer 0.107
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.491
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.752 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:13:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:13:29_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/12/artifact/build-artifacts/01:13:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:13:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/12/artifact/build-artifacts/01:13:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.239
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.082
And I corrupt the boot device's GPT backup header 0.202
And I power off the computer 0.260
When I start the computer 0.838
Then the computer boots Tails 38.477
When I log in to a new session 11.174
And all notifications have disappeared 7.053
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.145
And Tails detected partitioning error partitioning-corruption 0.004
After features/support/hooks.rb:335 0.996
After features/support/hooks.rb:104 0.007
Tags: @product
1:4.603
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.635
And I corrupt the boot device's GPT backup partition table 0.241
And I power off the computer 0.315
When I start the computer 0.778
Then the computer boots Tails 37.212
When I log in to a new session 11.413
And all notifications have disappeared 6.858
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.142
And Tails detected partitioning error partitioning-corruption 0.005
After features/support/hooks.rb:335 0.680
After features/support/hooks.rb:104 0.007
Tags: @product
1:40.178
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_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.011
And I plug USB drive "temp" 1.021
And I write the Tails USB image to disk "temp" 13.779
When I start Tails from USB drive "temp" with network unplugged 1:4.867
Then Tails is running from USB drive "temp" 0.540
And the Greeter forbids creating a persistent partition 0.047
When I log in to a new session 9.985
And all notifications have disappeared 7.170
Then I am recommended to reinstall Tails due to partitioning errors 0.181
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.199
And I am told that Persistent Storage cannot be created 1.289
And Tails detected partitioning error partitioning-corruption 0.008
After features/support/hooks.rb:335 0.984
After features/support/hooks.rb:104 0.126
Tags: @product
1:10.254
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
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.007
And I plug USB drive "temp" 1.016
And I write the Tails USB image to disk "temp" 13.900
When I start Tails from USB drive "temp" with network unplugged 54.347
Then Tails is running from USB drive "temp" 0.624
And the Greeter recommends reinstalling Tails due to partitioning errors 0.045
And the Greeter forbids starting Tails 0.035
And the Greeter forbids all settings but language 0.219
And Tails detected partitioning error guid-not-randomized 0.005
After features/support/hooks.rb:335 1.047
After features/support/hooks.rb:104 0.119
Tags: @product
1:6.946
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.062
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.010
And I plug USB drive "temp" 1.019
And I write the Tails USB image to disk "temp" 13.582
When I start Tails from USB drive "temp" with network unplugged 51.297
Then Tails is running from USB drive "temp" 0.645
And the Greeter recommends reinstalling Tails due to partitioning errors 0.055
And the Greeter forbids starting Tails 0.043
And the Greeter forbids all settings but language 0.223
And Tails detected partitioning error system-partition-not-resized 0.006
After features/support/hooks.rb:335 0.805
After features/support/hooks.rb:104 0.124
Tags: @product
1:1.063
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.018
Given a computer 0.062
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.010
And I plug USB drive "temp" 1.024
And I write the Tails USB image to disk "temp" 13.714
When I start Tails from USB drive "temp" with network unplugged 45.694
Then Tails is running from USB drive "temp" 0.260
And the Greeter recommends reinstalling Tails due to partitioning errors 0.043
And the Greeter forbids starting Tails 0.036
And the Greeter forbids all settings but language 0.210
And Tails detected partitioning error fs-not-resized 0.005
After features/support/hooks.rb:335 0.615
After features/support/hooks.rb:104 0.110