Bug #8317

fillram isn't effective for filling the memory in Jessie

Added by anonym 2014-11-26 19:11:43 . Updated 2015-11-24 16:22:02 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_2.0
Start date:
2014-11-26
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
268

Description

For instance, when running erase_memory.feature with a feature/jessie-based Tails image, we end up covering less than 55% of the ram in the “old computer” scenarios, despite there still being ~1300 MiB of free (non-buffer, non-cache) memory. This is getting too low and doesn’t feel reliable any more, IMHO.

Subtasks

Related issues

Blocks Tails - Bug #9705: Update the memory erasure automated tests for Jessie Resolved 2015-07-08 2016-01-15

History

#1 Updated by intrigeri 2014-11-27 09:24:47

  • blocks Feature #7563: Update the automated test suite for Jessie ISO images added

#2 Updated by intrigeri 2014-11-27 09:26:01

  • Assignee set to anonym

I believe that’s not a problem with fillram itself, but with the way it’s run in the automated test suite: when I tested memory erasure manually (https://tails.boum.org/contribute/release_process/test/erase_memory_on_shutdown/), it worked perfectly. Then assigning to anonym, as part of Feature #7563.

#3 Updated by anonym 2015-11-04 10:08:24

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)

This part is fixed now of what currently has been done for Bug #9705.

#4 Updated by intrigeri 2015-11-05 02:33:39

  • Category set to Test suite
  • Deliverable for set to 268

#5 Updated by intrigeri 2015-11-05 02:33:55

  • blocked by deleted (Feature #7563: Update the automated test suite for Jessie ISO images)

#6 Updated by intrigeri 2015-11-05 02:34:17

#7 Updated by intrigeri 2015-11-05 02:34:33

  • blocks Bug #9705: Update the memory erasure automated tests for Jessie added

#8 Updated by intrigeri 2015-11-24 16:22:02

  • % Done changed from 0 to 100