Project Number Date
test_Tails_ISO_devel 3812 15 May 2025, 09:49

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 18:24.251 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
40.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.960
Then the computer boots Tails 36.227
And I see a disk failure message on the splash screen 2.778
After features/support/hooks.rb:330 0.655
After features/support/hooks.rb:100 0.011
40.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.984
Then the computer boots Tails 35.908
And I see a disk failure message on the splash screen 3.652
After features/support/hooks.rb:330 0.698
After features/support/hooks.rb:100 0.010
40.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.257
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 1.034
Then the computer boots Tails 35.634
And I see a disk failure message on the splash screen 3.311
After features/support/hooks.rb:330 0.667
After features/support/hooks.rb:100 0.009
Tags: @product @doc
1:24.821
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.197
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:24.623
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:330 6.060

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:11:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:11:47_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_devel/3812/artifact/build-artifacts/02:11:47_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:11:47_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:11:47_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:15.273
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.219
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.054
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:330 6.005

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:13:08)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:13:08_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_devel/3812/artifact/build-artifacts/02:13:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:13:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:13:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:24.788
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.219
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:24.569
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:330 5.685

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:14:39)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:14:39_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_devel/3812/artifact/build-artifacts/02:14:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:14:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:14:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:48.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.943
And I corrupt the boot device's GPT backup header 0.318
And I power off the computer 0.335
When I start the computer 1.049
Then the computer boots Tails 1:12.597
When I log in to a new session 18.302
And all notifications have disappeared 6.838
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.215
And Tails detected partitioning error partitioning-corruption 0.012
After features/support/hooks.rb:330 0.656
After features/support/hooks.rb:100 0.009
Tags: @product
1:50.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.759
And I corrupt the boot device's GPT backup partition table 0.341
And I power off the computer 0.337
When I start the computer 1.015
Then the computer boots Tails 1:12.459
When I log in to a new session 18.966
And all notifications have disappeared 8.254
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.271
And Tails detected partitioning error partitioning-corruption 0.046
After features/support/hooks.rb:330 1.174
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
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.048
And I plug USB drive "temp" 1.054
And I write the Tails USB image to disk "temp" 31.793
When I start Tails from USB drive "temp" with network unplugged 1:39.095
Then Tails is running from USB drive "temp" 0.352
And the Greeter forbids creating a persistent partition 0.098
When I log in to a new session 17.293
And all notifications have disappeared 7.310
Then I am recommended to reinstall Tails due to partitioning errors 0.206
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.251
And I am told that Persistent Storage cannot be created 2.838
And Tails detected partitioning error partitioning-corruption 0.021
After features/support/hooks.rb:330 1.192
After features/support/hooks.rb:100 0.105
Tags: @product
2:13.233
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
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.047
And I plug USB drive "temp" 1.048
And I write the Tails USB image to disk "temp" 29.051
When I start Tails from USB drive "temp" with network unplugged 1:42.062
Then Tails is running from USB drive "temp" 0.331
And the Greeter recommends reinstalling Tails due to partitioning errors 0.079
And the Greeter forbids starting Tails 0.066
And the Greeter forbids all settings but language 0.331
And Tails detected partitioning error guid-not-randomized 0.012
After features/support/hooks.rb:330 0.862
After features/support/hooks.rb:100 0.133
Tags: @product
1:59.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
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.052
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 27.876
When I start Tails from USB drive "temp" with network unplugged 1:29.340
Then Tails is running from USB drive "temp" 0.352
And the Greeter recommends reinstalling Tails due to partitioning errors 0.090
And the Greeter forbids starting Tails 0.087
And the Greeter forbids all settings but language 0.338
And Tails detected partitioning error system-partition-not-resized 0.012
After features/support/hooks.rb:330 0.882
After features/support/hooks.rb:100 0.157
Tags: @product
1:44.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.243
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.064
And I plug USB drive "temp" 1.057
And I write the Tails USB image to disk "temp" 27.855
When I start Tails from USB drive "temp" with network unplugged 1:14.804
Then Tails is running from USB drive "temp" 0.361
And the Greeter recommends reinstalling Tails due to partitioning errors 0.078
And the Greeter forbids starting Tails 0.131
And the Greeter forbids all settings but language 0.345
And Tails detected partitioning error fs-not-resized 0.012
After features/support/hooks.rb:330 0.703
After features/support/hooks.rb:100 0.168