Bad pool bugcheck at 3rd stage boot, repeatable at subsequent restarts. Doesn't seem to be present when i issued retesting of that rev.
Regards
On Wed, Feb 22, 2012, at 12:44 AM, buildbot(a)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/4876
>
> 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: 55800
> Blamelist: jgardou
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
VBox window hanged hard, at STOPPING. Sysreg could not restart it. Nothing happened even after vbox process being killed.
----- Original message -----
From: buildbot(a)reactos.org
To: ros-builds(a)reactos.org
Date: Tue, 21 Feb 2012 11:31:15 +0000
Subject: [ros-builds] Windows_AMD64_1 VBox-Test: build failed
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/4844
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: 55770
Blamelist: jgardou
BUILD FAILED: failed test
sincerely,
-The Buildbot
--
With best regards
Caemyr
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(a)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
>
>
>
--
With best regards
Caemyr
Another ghost:
[100%] Building C object drivers/wdm/audio/sysaudio/CMakeFiles/sysaudio.dir/dispatcher.c.obj
Failed to read source file: 0
mingw32-make.exe[3]: *** [boot/freeldr/freeldr/frldr16.bin] Error -4
mingw32-make.exe[2]: *** [boot/freeldr/freeldr/CMakeFiles/freeldr.dir/all] Error 2
mingw32-make.exe[2]: *** Waiting for unfinished jobs....
On Tue, Feb 21, 2012, at 11:36 AM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed build on builder CMake_x86_GCCWin
> Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/CMake_x86_GCCWin%20Debug/builds/2729
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 55775
> Blamelist: janderwald
>
> BUILD FAILED: failed building bootcd
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
1. Time machines have not been invented so that's impossible.
2. I don't live in the past so that was stupid
3. I have my date/time done perfectly fine.
So next time don't say that to someone knows what they are talking about
I am planning on running because my school pc has 1.72gb of ram but I can't put a new os on physicle disk my parents will get very mad if I install os but not if I run it on cd.
Oh bye I have to go to bed in 6 minutes