Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 47 27 Aug 2024, 14:24

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 8:39.307 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
44.534
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start the computer from DVD with network unplugged 39.760
When Tails detects disk read failures on the SquashFS 1.395
Then I see a disk failure message on the splash screen 3.179
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.011
Tags: @product
42.112
Before features/support/hooks.rb:269 0.005
Given a computer 0.243
And I start the computer from DVD with network unplugged 38.954
When Tails detects disk read failures on the boot device 0.819
Then I see a disk failure message on the splash screen 2.094
After features/support/hooks.rb:326 0.621
After features/support/hooks.rb:100 0.013
Tags: @product
42.080
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I start the computer from DVD with network unplugged 38.323
When Tails detects disk read failures on the boot device with a target error 1.917
Then I see a disk failure message on the splash screen 1.604
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.010
Tags: @product @doc
2:9.926
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.233
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:9.692
try_for() 
try_for() timeout expired (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 6.034 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:05:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/02:05:38_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/47/artifact/build-artifacts/02:05:38_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/47/artifact/build-artifacts/02:05:38_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/47/artifact/build-artifacts/02:05:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
2:10.689
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.008
Steps
Given a computer 0.277
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:10.412
try_for() 
try_for() timeout expired (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.206 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:07:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/02:07:54_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/47/artifact/build-artifacts/02:07:54_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/47/artifact/build-artifacts/02:07:54_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/47/artifact/build-artifacts/02:07:54_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
2:9.964
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.195
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:9.768
try_for() 
try_for() timeout expired (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.236 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:10:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/02:10:09_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/47/artifact/build-artifacts/02:10:09_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/47/artifact/build-artifacts/02:10:09_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/47/artifact/build-artifacts/02:10:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000