Project

General

Profile

Bug #9329

Bug #8059: Windows Camouflage automated tests sometimes failed due to differently ordered icons in the notification area

fillram sometimes doesn't complete

Added by intrigeri over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Test suite
Target version:
Start date:
05/03/2015
Due date:
% Done:

100%

Feature Branch:
test/9329-fillram-crashes
Type of work:
Code
Blueprint:
Starter:
Affected tool:

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

erase_memory-2015-05-03T10_08_27-04_00.png View (41.3 KB) intrigeri, 05/03/2015 08:44 AM

Associated revisions

Revision 09947898
Added by intrigeri over 4 years ago

Merge remote-tracking branch 'origin/test/9329-fillram-crashes' into stable

Fix-committed: #9329

History

#2 Updated by anonym over 4 years ago

  • 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 over 4 years ago

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

#4 Updated by intrigeri over 4 years ago

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

Merged!

#5 Updated by intrigeri about 4 years ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF