Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 3 24 Jul 2024, 19:22

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Emergency shutdown 28 1 7 0 0 36 4 1 5 5:53.167 Failed
Tags: @product @not_release_blocker
Feature Emergency shutdown
As a Tails user when I unplug my Tails device to trigger emergency shutdown I want the system memory to be free from sensitive data.
Tags: @product @not_release_blocker
1:0.636
Before features/support/hooks.rb:269 0.004
Given I have started Tails from DVD and logged in and the network is connected 48.508
When I eject the boot medium 0.227
Then Tails eventually shuts down 11.900
After features/support/hooks.rb:326 0.235
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
48.468
Before features/support/hooks.rb:269 0.006
Given I have started Tails from DVD without network and logged in 9.810
And I prepare Tails for memory erasure tests 0.573
And I fill a 128 MiB file with a known pattern on the root filesystem 20.475
And patterns cover at least 128 MiB in the guest's memory 4.313 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I eject the boot medium 0.377
And I wait for Tails to finish wiping the memory 11.144
Then I find very few patterns in the guest's memory 1.773 
Pattern coverage: 0.000% (0 MiB out of 885 MiB reference memory)
After features/support/hooks.rb:326 3.631
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
39.881
Before features/support/hooks.rb:269 0.005
Given I have started Tails from DVD without network and logged in 8.480
And I prepare Tails for memory erasure tests 0.621
And I plug and mount a 128 MiB USB drive with a vfat filesystem 9.330
And I fill the USB drive with a known pattern 3.405
And I read the content of the test FS 0.138
And patterns cover at least 90% of the test FS size in the guest's memory 4.584 
Pattern coverage: 97.924% (124 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.313
And I wait for Tails to finish wiping the memory 11.098
Then I find very few patterns in the guest's memory 1.907 
Pattern coverage: 0.000% (0 MiB out of 866 MiB reference memory)
After features/support/hooks.rb:326 3.576
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
1:12.941
Before features/support/hooks.rb:269 0.004
Given I have started Tails from DVD without network and logged in 10.288
And I prepare Tails for memory erasure tests 0.660
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 38.321
And I fill the USB drive with a known pattern 1.545
And I read the content of the test FS 0.083
And patterns cover at least 99% of the test FS size in the guest's memory 3.562 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.505
And I wait for Tails to finish wiping the memory 16.113
Then I find very few patterns in the guest's memory 1.860 
Pattern coverage: 0.000% (0 MiB out of 888 MiB reference memory)
After features/support/hooks.rb:326 3.620
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
2:11.239
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:11.239
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/usb.rb:685: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:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708: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:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708: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/emergency_shutdown.feature:48:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
And I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
And patterns cover at least 100 MiB in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:326 6.984 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 01:45:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000