Bug #9329
fillram sometimes doesn't complete
Start date:
2015-05-03
Due date:
% Done:
100%
Description
On Tails 1.4~rc1:
Scenario: Anti-test: no memory erasure on a modern computer # features/erase_memory.feature:7
Given a computer # features/step_definitions/common_steps.rb:66
And the computer is a modern 64-bit system # features/step_definitions/erase_memory.rb:1
And the computer has 8 GiB of RAM # features/step_definitions/common_steps.rb:71
And I set Tails to boot with options "debug=wipemem" # features/step_definitions/common_steps.rb:134
And I start Tails from DVD with network unplugged and I login # features/step_definitions/common_steps.rb:147
Then the PAE kernel is running # features/step_definitions/erase_memory.rb:24
And at least 8 GiB of RAM was detected # features/step_definitions/erase_memory.rb:44
Detected 8003 MiB of RAM
And process "memlockd" is running # features/step_definitions/common_steps.rb:450
And process "udev-watchdog" is running # features/step_definitions/common_steps.rb:450
Memory fill progress: 89%
When I fill the guest's memory with a known pattern without verifying # features/step_definitions/erase_memory.rb:77
fillram didn't complete, probably the VM crashed (Timeout::Error)
./features/support/helpers/misc_helpers.rb:66:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:24:in `try_for'
./features/step_definitions/erase_memory.rb:117:in `/^I fill the guest's memory with a known pattern(| without verifying)$/'
features/erase_memory.feature:17:in `When I fill the guest's memory with a known pattern without verifying'
And I reboot without wiping the memory # features/step_definitions/erase_memory.rb:156
Then I find many patterns in the guest's memory # features/step_definitions/erase_memory.rb:147
Files
Subtasks
History
#1 Updated by intrigeri 2015-05-03 08:45:33
- blocks #8538 added
#2 Updated by anonym 2015-06-12 14:30:35
- Status changed from Confirmed to In Progress
- Assignee changed from anonym to intrigeri
- % Done changed from 0 to 50
- QA Check set to Ready for QA
- Feature Branch set to test/9329-fillram-crashes
- Type of work changed from Research to Code
I pushed some fixes for everything I could think of related to this.
#3 Updated by intrigeri 2015-06-12 17:53:30
- Status changed from In Progress to Fix committed
- % Done changed from 50 to 100
Applied in changeset commit:099478982d471d656f14f878c2266f9cef4e2c70.
#4 Updated by intrigeri 2015-06-12 17:55:14
- Assignee deleted (
intrigeri) - QA Check changed from Ready for QA to Pass
Merged!
#5 Updated by intrigeri 2015-07-03 03:41:00
- Status changed from Fix committed to Resolved