Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 23rd of February, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting. Note that the IRC service will only be started
shortly before the meeting. Your participation passwords will be emailed
to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. Volunteers welcome.
Proposed agenda for the meeting:
1. Release status: 0.3.15
2. New website status and migration plans.
3. CMake migration and finally abandoning RBuild.
4. 0.3.14 release party.
More suggestions are welcome as usual.
With the best regards,
Aleksey Bragin.
i changed email to this one microsoft windows live is better than google.
now i saved the best part for last, go her for a list of win32 api functions:
http://j00ru.vexillium.org/w32k_syscalls/
it will help a lot in the development of reactos and make a lot mor programs run on then system
2nd stage pool corruption at the end, CM assert at subsequent reboots. I restarted the test and it worked fine the second time.
On Wed, Feb 22, 2012, at 05:28 PM, 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/4888
>
> 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: 55808
> Blamelist: sginsberg
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
VBox was locked up. Usurp: could you look into it? VBox window is stuck with Stopping status. Perhaps sysreg should kill the whole process and restart it, just to be safe?
Best regards
On Wed, Feb 22, 2012, at 12:15 PM, 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/4882
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_2
>
> Build Reason: The web-page 'force build' button was pressed by 'osiejka':
>
> Build Source Stamp: 55804
> Blamelist:
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
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