Project Number Date
test_Tails_ISO_21548-flatpak-install 16 22 May 2026, 18:09

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.374 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.288
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.067
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.848
Then the computer boots Tails 26.510
And I see a disk failure message on the splash screen 2.861
After features/support/hooks.rb:335 0.942
After features/support/hooks.rb:104 0.006
Tags: @product @broken_welcome_screen
28.071
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.071
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.761
Then the computer boots Tails 25.441
And I see a disk failure message on the splash screen 1.796
After features/support/hooks.rb:335 0.892
After features/support/hooks.rb:104 0.008
Tags: @product @broken_welcome_screen
28.888
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.073
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.738
Then the computer boots Tails 26.771
And I see a disk failure message on the splash screen 1.304
After features/support/hooks.rb:335 0.858
After features/support/hooks.rb:104 0.010
Tags: @product @doc
34.130
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.080
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 34.049
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.816 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:14:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:14:40_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/16/artifact/build-artifacts/01:14:40_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:14:40_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:14:40_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
32.636
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.080
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.555
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.955 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:15:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:15:17_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/16/artifact/build-artifacts/01:15:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:15:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:15:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
32.992
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.088
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.904
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 5.089 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:15:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:15:55_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/16/artifact/build-artifacts/01:15:55_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:15:55_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:15:55_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.510
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 7.493
And I corrupt the boot device's GPT backup header 0.212
And I power off the computer 0.265
When I start the computer 0.779
Then the computer boots Tails 37.571
When I log in to a new session 12.194
And all notifications have disappeared 6.845
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.691
After features/support/hooks.rb:104 0.007
Tags: @product
1:5.256
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 7.230
And I corrupt the boot device's GPT backup partition table 0.279
And I power off the computer 0.275
When I start the computer 0.880
Then the computer boots Tails 37.825
When I log in to a new session 11.797
And all notifications have disappeared 6.793
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.165
And Tails detected partitioning error partitioning-corruption 0.006
After features/support/hooks.rb:335 0.970
After features/support/hooks.rb:104 0.017
Tags: @product
1:46.127
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Given a computer 0.201
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.047
And I plug USB drive "temp" 1.038
And I write the Tails USB image to disk "temp" 14.050
When I start Tails from USB drive "temp" with network unplugged 1:9.817
Then Tails is running from USB drive "temp" 0.596
And the Greeter forbids creating a persistent partition 0.065
When I log in to a new session 10.162
And all notifications have disappeared 7.004
Then I am recommended to reinstall Tails due to partitioning errors 0.149
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.253
And I am told that Persistent Storage cannot be created 1.735
And Tails detected partitioning error partitioning-corruption 0.004
After features/support/hooks.rb:335 1.088
After features/support/hooks.rb:104 0.135
Tags: @product
1:6.553
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.077
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.012
And I plug USB drive "temp" 1.020
And I write the Tails USB image to disk "temp" 14.019
When I start Tails from USB drive "temp" with network unplugged 50.596
Then Tails is running from USB drive "temp" 0.540
And the Greeter recommends reinstalling Tails due to partitioning errors 0.049
And the Greeter forbids starting Tails 0.031
And the Greeter forbids all settings but language 0.201
And Tails detected partitioning error guid-not-randomized 0.005
After features/support/hooks.rb:335 0.731
After features/support/hooks.rb:104 0.142
Tags: @product
1:9.149
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
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.012
And I plug USB drive "temp" 1.019
And I write the Tails USB image to disk "temp" 14.409
When I start Tails from USB drive "temp" with network unplugged 52.636
Then Tails is running from USB drive "temp" 0.641
And the Greeter recommends reinstalling Tails due to partitioning errors 0.053
And the Greeter forbids starting Tails 0.063
And the Greeter forbids all settings but language 0.234
And Tails detected partitioning error system-partition-not-resized 0.006
After features/support/hooks.rb:335 0.619
After features/support/hooks.rb:104 0.173
Tags: @product
1:7.768
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.068
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.009
And I plug USB drive "temp" 1.022
And I write the Tails USB image to disk "temp" 13.937
When I start Tails from USB drive "temp" with network unplugged 51.860
Then Tails is running from USB drive "temp" 0.570
And the Greeter recommends reinstalling Tails due to partitioning errors 0.046
And the Greeter forbids starting Tails 0.028
And the Greeter forbids all settings but language 0.219
And Tails detected partitioning error fs-not-resized 0.005
After features/support/hooks.rb:335 1.014
After features/support/hooks.rb:104 0.119