Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 8 27 Jul 2024, 17:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 15 3 9 0 0 27 3 3 6 9:17.221 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
42.654
Before features/support/hooks.rb:269 0.008
Given a computer 0.246
And I start the computer from DVD with network unplugged 38.511
When Tails detects disk read failures on the SquashFS 0.677
Then I see a disk failure message on the splash screen 3.219
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.012
Tags: @product
42.435
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start the computer from DVD with network unplugged 38.301
When Tails detects disk read failures on the boot device 0.911
Then I see a disk failure message on the splash screen 3.017
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.011
Tags: @product
40.805
Before features/support/hooks.rb:269 0.008
Given a computer 0.245
And I start the computer from DVD with network unplugged 36.430
When Tails detects disk read failures on the boot device with a target error 1.547
Then I see a disk failure message on the splash screen 2.581
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.011
Tags: @product @doc
2:37.011
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.216
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:36.794
try_for() 
try_for() timeout expired
Last ignored exception was: Test::Unit::AssertionFailedError: <false> is not true.
./features/step_definitions/usb.rb:684:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:683:in `block in <top (required)>'
./features/step_definitions/usb.rb:702:in `block in <top (required)>'
./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 `block (2 levels) in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./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:27:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:21: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:326 5.346 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:03:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:03:53_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_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:03:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:03:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:03:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
2:9.616
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.210
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:9.406
try_for() 
try_for() timeout expired
Last ignored exception was: Test::Unit::AssertionFailedError: <false> is not true.
./features/step_definitions/usb.rb:684:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:683:in `block in <top (required)>'
./features/step_definitions/usb.rb:702:in `block in <top (required)>'
./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 `block (2 levels) in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./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:28:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:21: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:326 5.209 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:06:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:06: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_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:06:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:06:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:06:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
2:24.697
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.010
Steps
Given a computer 0.290
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:24.407
try_for() 
try_for() timeout expired
Last ignored exception was: Test::Unit::AssertionFailedError: <false> is not true.
./features/step_definitions/usb.rb:684:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:683:in `block in <top (required)>'
./features/step_definitions/usb.rb:702:in `block in <top (required)>'
./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 `block (2 levels) in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./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:21: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:326 5.325 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:08:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:08:38_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_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:08:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:08:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/8/artifact/build-artifacts/02:08:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000