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
I have taken into account the stuff you all sent about system specs since the pc will be mine at the end of my school year I am saving up for:
8gb of ram.
Some new hdds of over 80gb
I don't know how to add a new cpu, and they are very expensive.
Mikey
P.s.
Will a .iso work to make a live cd or usb boot cd,
I know I can do it with linux distros but not ReactOS.
Hello I am new here what are the system minimum specs as I have old system for development.
My dad says I get the old system at the ent of my school if I get good grades it has ubuntu 11.10 but it is slow I like to call it u-slow-os 1.6.
Epic.
On 16.02.2012 15:16, jgardou(a)svn.reactos.org wrote:
> Author: jgardou
> Date: Thu Feb 16 11:16:10 2012
> New Revision: 55631
>
> URL: http://svn.reactos.org/svn/reactos?rev=55631&view=rev
> Log:
> [NTOSKRNL/MM]
> - use ARM3 allocation for PDE pages.
> There is now one table for system PDEs, and their pages are not leaked anymore.
> Also fix bug 5857 (aka mshtml bug).
> Only for x86 now. Timo, I think you should do it for amd64 as well.
> Thanks for your patience, go back to testing now.
> A huge congrats to Cameron and Thomas, without them I wouldn't even have dared touching this code.
>
> Modified:
> trunk/reactos/ntoskrnl/mm/ARM3/virtual.c
> trunk/reactos/ntoskrnl/mm/i386/page.c
>
Hi,
due to popular request, a new ML is available (for read-only):
ros-builds. This ML will receive notifications sent by buildbot in case
of build breakge/tests breakage.
More notifications should be added any time soon.
For subscription, just go here:
http://reactos.org/mailman/listinfo/ros-builds
Regards,
Pierre
Hello,
during recent discussion, a topic about mailing lists appeared.
According to Pierre, we have 6 totally unused mailing lists, which are:
ros-cis
ros-errors
ros-kernel
ros-svn-diffs
ros-translate
ros-foundation
I propose to delete all those, maybe except for ros-foundation.
Any opinions?
WBR,
Aleksey Bragin.
Historical commit, deserving a nice rev number too!
(hmm, 69 maybe viewed by some as nice too, but better let's focus on the
"555" part ;))
On 12.02.2012 22:34, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Sun Feb 12 18:34:05 2012
> New Revision: 55569
>
> URL: http://svn.reactos.org/svn/reactos?rev=55569&view=rev
> Log:
> [USBDRV]
> - Terminate the NT4 USB driver
>
> Removed:
> trunk/reactos/drivers/usb/nt4compat/
>
>
Hi,
as requested I added a blacklisting ability to testman. The purpose of
this is to have some meaningful comparison between test runs without
completely disabling randomly behaving test sets. This means that
blacklisted test are still being run, logged and included in the Totals
summary. They won't affect the newly added "nonblacklisted summary"
only. The last thing needed before we can actually benefit from this is
to go through the tests, find those that give random results and either
fix them or add them to the blacklist. Please use this wiki page
http://www.reactos.org/wiki/Testman_blacklist to forge the list. Anyone
with web repo commit access (that includes me) can then update the
config itself.
WBR,
Kamil
Hi,
ok... last but not least, RosBE for Windows Version 2.0 is out too.
This is one of the last steps to the upcoming cmake switch with dumping rbuild fully and forever.
The setup files can be found here:
http://www.reactos.org/wiki/Build_Environment
Setup is the same good known NSIS based one for now. Just remove the old BE and let it install it over.
CMAKE usage instructions are here:http://reactos.org/wiki/CMake
Big thanks for this release goes to Heis and Colin from the Unix BE team, Amine for not killing me taking so long for a release and dralnix and blight_ for doing the first steps to a advanced BE years ago. Miss you, guys ^^
As for Unix one, I fully dump the support for any earlier Version of RosBE Windows starting from NOW.
Best regards,
Daniel
Hi,
finally, we are getting closer and closer to CMake switch. RosBE-2.0
release brings supports for CMake and all the changes made in the tool
chain. You can find it here:
https://sourceforge.net/projects/reactos/files/RosBE-Unix/2.0/
To install it, simply extract the tar.bz2, and then run the
RosBE-Builder.sh script.
For instructions about how to use CMake in ReactOS, have a look to that
wiki page: http://reactos.org/wiki/CMake
Regarding this release, I would like to thank Colin Finck who did
everything for it, but who have been obliged to let me release his work
due to his busy life.
RosBE 1.5 is not supported any longer.
And I invite everyone to switch to CMake (with RosBE2.0 Windows/Linux).
Rbuild deletion is now a matter of days.
The countdown for Rbuild deletion has started.
Regards,
Pierre
I must say, hpoussin proposed to get rid of bget in favor of rtl/heap.c,
and I criticized his idea because I had no trust in the old heap code.
Would reusing the new code be an option? Or you already invented the
"mini-heap" which works good enough?
WBR,
Aleksey.
On 10.02.2012 0:01, tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Thu Feb 9 20:01:10 2012
> New Revision: 55518
>
> URL: http://svn.reactos.org/svn/reactos?rev=55518&view=rev
> Log:
> [FREELDR]
> - Enable new heap code and cleanup the heap, releasing unused memory, before starting reactos
> - Gives our kernel about 4MB additional memory, which - at the current leak rate - means around 8 minutes longer before it runs out of memory :)
> - Using the temp heap for all temporary allocations should increase the amount of saved space
>
> Removed:
> trunk/reactos/boot/freeldr/freeldr/mm/heap.c
> trunk/reactos/boot/freeldr/freeldr/rtl/bget.c
>
Hi all,
The Google Summer of Code 2012 project registration phase is starting in
three weeks.
Are we going to apply again after our success last year?
Who will be available as administrators and mentors?
Is anybody already collecting task ideas?
Cheers,
Colin