Yet another CM fsckup:
*** Fatal System Error: 0x00000019 (0x00000005,0xE11FF880,0x000000F0,0xE11FF798) at end of 2nd stage. At subsequent reboots: Assertion 'KeyCell->Signature == CM_KEY_NODE_SIGNATURE' failed at P:\Trunk_slave\x86_CMake\build\lib\cmlib\cminit.c line 115
We really need something to fight the pool corruptions, Aleksiej.
Testing will be restarted.
Best regards
On Tue, Feb 21, 2012, at 11:50 AM, buildbot@reactos.org wrote:
The Buildbot has detected a failed build on builder Windows_AMD64_1 VBox-Test while building ReactOS. Full details are available at: http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/4845
Buildbot URL: http://build.reactos.org/
Buildslave for this Build: Windows_AMD64_2
Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger) Build Source Stamp: 55771 Blamelist: jgardou
BUILD FAILED: failed test
sincerely, -The Buildbot
For the record, it also happens really often on KVM (see all the failed tests recently).
Le mardi 21 février 2012 à 13:12 +0100, caemyr@myopera.com a écrit :
Yet another CM fsckup:
*** Fatal System Error: 0x00000019 (0x00000005,0xE11FF880,0x000000F0,0xE11FF798) at end of 2nd stage. At subsequent reboots: Assertion 'KeyCell->Signature == CM_KEY_NODE_SIGNATURE' failed at P:\Trunk_slave\x86_CMake\build\lib\cmlib\cminit.c line 115
We really need something to fight the pool corruptions, Aleksiej.
Testing will be restarted.
Best regards
On Tue, Feb 21, 2012, at 11:50 AM, buildbot@reactos.org wrote:
The Buildbot has detected a failed build on builder Windows_AMD64_1 VBox-Test while building ReactOS. Full details are available at: http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/4845
Buildbot URL: http://build.reactos.org/
Buildslave for this Build: Windows_AMD64_2
Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger) Build Source Stamp: 55771 Blamelist: jgardou
BUILD FAILED: failed test
sincerely, -The Buildbot