Project Number Date
test_Tails_ISO_21548-flatpak-install 15 22 May 2026, 17:33

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:35.414 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
28.142
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.104
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.776
Then the computer boots Tails 25.725
And I see a disk failure message on the splash screen 1.535
After features/support/hooks.rb:335 0.668
After features/support/hooks.rb:104 0.007
Tags: @product @broken_welcome_screen
30.857
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.066
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.801
Then the computer boots Tails 26.695
And I see a disk failure message on the splash screen 3.294
After features/support/hooks.rb:335 0.921
After features/support/hooks.rb:104 0.012
Tags: @product @broken_welcome_screen
29.452
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given a computer 0.063
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.860
Then the computer boots Tails 25.284
And I see a disk failure message on the splash screen 3.244
After features/support/hooks.rb:335 0.760
After features/support/hooks.rb:104 0.006
Tags: @product @doc
33.632
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.062
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 33.569
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.050 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:12:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:12:18_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/15/artifact/build-artifacts/01:12:18_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:12:18_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:12:18_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
32.833
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Steps
Given a computer 0.120
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.712
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 5.056 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:12:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:12:56_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/15/artifact/build-artifacts/01:12:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:12:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:12:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:104 0.000
Tags: @product @doc
34.979
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.068
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 34.910
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.877 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:13:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:13:36_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/15/artifact/build-artifacts/01:13:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:13:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/15/artifact/build-artifacts/01:13:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.458
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.622
And I corrupt the boot device's GPT backup header 0.308
And I power off the computer 0.282
When I start the computer 0.889
Then the computer boots Tails 40.450
When I log in to a new session 11.390
And all notifications have disappeared 7.342
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.163
And Tails detected partitioning error partitioning-corruption 0.009
After features/support/hooks.rb:335 0.907
After features/support/hooks.rb:104 0.010
Tags: @product
1:9.880
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.166
And I corrupt the boot device's GPT backup partition table 0.232
And I power off the computer 0.260
When I start the computer 0.759
Then the computer boots Tails 39.371
When I log in to a new session 13.668
And all notifications have disappeared 7.280
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.132
And Tails detected partitioning error partitioning-corruption 0.007
After features/support/hooks.rb:335 0.899
After features/support/hooks.rb:104 0.009
Tags: @product
1:42.601
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.080
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.014
And I plug USB drive "temp" 1.036
And I write the Tails USB image to disk "temp" 14.640
When I start Tails from USB drive "temp" with network unplugged 1:4.317
Then Tails is running from USB drive "temp" 0.634
And the Greeter forbids creating a persistent partition 0.050
When I log in to a new session 11.611
And all notifications have disappeared 7.084
Then I am recommended to reinstall Tails due to partitioning errors 0.133
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.205
And I am told that Persistent Storage cannot be created 1.786
And Tails detected partitioning error partitioning-corruption 0.005
After features/support/hooks.rb:335 1.145
After features/support/hooks.rb:104 0.169
Tags: @product
1:9.639
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.064
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.009
And I plug USB drive "temp" 1.020
And I write the Tails USB image to disk "temp" 13.779
When I start Tails from USB drive "temp" with network unplugged 53.851
Then Tails is running from USB drive "temp" 0.560
And the Greeter recommends reinstalling Tails due to partitioning errors 0.053
And the Greeter forbids starting Tails 0.040
And the Greeter forbids all settings but language 0.253
And Tails detected partitioning error guid-not-randomized 0.005
After features/support/hooks.rb:335 0.613
After features/support/hooks.rb:104 0.129
Tags: @product
1:2.837
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.077
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.025
And I write the Tails USB image to disk "temp" 13.805
When I start Tails from USB drive "temp" with network unplugged 47.137
Then Tails is running from USB drive "temp" 0.507
And the Greeter recommends reinstalling Tails due to partitioning errors 0.045
And the Greeter forbids starting Tails 0.031
And the Greeter forbids all settings but language 0.191
And Tails detected partitioning error system-partition-not-resized 0.005
After features/support/hooks.rb:335 0.927
After features/support/hooks.rb:104 0.119
Tags: @product
1:12.098
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.008
And I plug USB drive "temp" 1.018
And I write the Tails USB image to disk "temp" 14.427
When I start Tails from USB drive "temp" with network unplugged 55.656
Then Tails is running from USB drive "temp" 0.607
And the Greeter recommends reinstalling Tails due to partitioning errors 0.093
And the Greeter forbids starting Tails 0.048
And the Greeter forbids all settings but language 0.170
And Tails detected partitioning error fs-not-resized 0.006
After features/support/hooks.rb:335 0.676
After features/support/hooks.rb:104 0.203