Project Number Date
test_Tails_ISO_19139-arti-bridges 1 16 Nov 2024, 21:48

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Emergency shutdown 33 1 2 0 0 36 4 1 5 6:9.591 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:14.476
Scenario Tails shuts down on DVD boot medium removal
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:14.476
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:656:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:611:in `/^Tor is ready$/'
./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\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/emergency_shutdown.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
When I eject the boot medium 0.000
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:326 8.389 
SCENARIO FAILED: 'Tails shuts down on DVD boot medium removal' (at time 01:34:14)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/1/artifact/build-artifacts/01:34:14_Tails_shuts_down_on_DVD_boot_medium_removal_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/1/artifact/build-artifacts/01:34:14_Tails_shuts_down_on_DVD_boot_medium_removal.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/1/artifact/build-artifacts/01:34:14_Tails_shuts_down_on_DVD_boot_medium_removal.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/1/artifact/build-artifacts/01:34:14_Tails_shuts_down_on_DVD_boot_medium_removal.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/1/artifact/build-artifacts/01:34:14_Tails_shuts_down_on_DVD_boot_medium_removal.journal
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
43.584
Before features/support/hooks.rb:269 0.004
Given I have started Tails from DVD without network and logged in 8.452
And I prepare Tails for memory erasure tests 0.522
And I fill a 128 MiB file with a known pattern on the root filesystem 16.801
And patterns cover at least 128 MiB in the guest's memory 4.204 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I eject the boot medium 0.292
And I wait for Tails to finish wiping the memory 12.495
Then I find very few patterns in the guest's memory 0.815 
Pattern coverage: 0.000% (0 MiB out of 890 MiB reference memory)
After features/support/hooks.rb:326 3.627
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
40.750
Before features/support/hooks.rb:269 0.003
Given I have started Tails from DVD without network and logged in 8.605
And I prepare Tails for memory erasure tests 0.523
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.615
And I fill the USB drive with a known pattern 2.549
And I read the content of the test FS 0.116
And patterns cover at least 90% of the test FS size in the guest's memory 4.509 
Pattern coverage: 100.000% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.293
And I wait for Tails to finish wiping the memory 12.756
Then I find very few patterns in the guest's memory 0.781 
Pattern coverage: 0.000% (0 MiB out of 888 MiB reference memory)
After features/support/hooks.rb:326 3.584
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
1:2.411
Before features/support/hooks.rb:269 0.003
Given I have started Tails from DVD without network and logged in 8.196
And I prepare Tails for memory erasure tests 0.464
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 36.083
And I fill the USB drive with a known pattern 1.698
And I read the content of the test FS 0.058
And patterns cover at least 99% of the test FS size in the guest's memory 3.445 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.397
And I wait for Tails to finish wiping the memory 11.152
Then I find very few patterns in the guest's memory 0.915 
Pattern coverage: 0.000% (0 MiB out of 890 MiB reference memory)
After features/support/hooks.rb:326 3.592
After features/support/hooks.rb:100 0.000
Tags: @product @not_release_blocker
2:28.368
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.704
And I prepare Tails for memory erasure tests 1.463
And I fill a 128 MiB file with a known pattern on the persistent filesystem 29.319
And patterns cover at least 100 MiB in the guest's memory 4.320 
Pattern coverage: 115.863% (115 MiB out of 100 MiB reference memory)
When I eject the boot medium 0.454
And I wait for Tails to finish wiping the memory 11.116
Then I find very few patterns in the guest's memory 0.812 
Pattern coverage: 0.000% (0 MiB out of 880 MiB reference memory)
And Tails eventually shuts down 1:30.177
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.000