Re: [ros-dev] Problems with patchbot/newcc/rosbe

2012-03-06 Thread Timo Kreuzer
Am 06.03.2012 01:11, schrieb cae...@myopera.com: After a quick look into your problems with patchbot it seems that vbox scripts were missing some errorlevel checks, which should bail out the test run at prepare stage when ISO was not present (which is the situation when you dont pass the

Re: [ros-dev] Problems with patchbot/newcc/rosbe

2012-03-06 Thread Timo Kreuzer
Am 06.03.2012 01:20, schrieb Zachary Gorden: Would also be nice if we could turn off the whole sound alert thing. Some of us find it a bit irritating. Some of us also find it a bit useful. ___ Ros-dev mailing list Ros-dev@reactos.org

Re: [ros-dev] Problems with patchbot/newcc/rosbe

2012-03-06 Thread Daniel Reimer
I think our mingw32-make is the problem. Even if you ONLY use mingw32-make it does not return what it should... Am 06.03.2012 10:08, schrieb Timo Kreuzer: Am 06.03.2012 01:11, schrieb cae...@myopera.com: After a quick look into your problems with patchbot it seems that vbox scripts were

Re: [ros-dev] Problems with patchbot/newcc/rosbe

2012-03-06 Thread caemyr
Could someone doublecheck that? My builder is using a custom PGO build of mingw32-make. It is vital to be sure if this issue is local or general. On Tue, Mar 6, 2012, at 10:20 PM, Daniel Reimer wrote: I think our mingw32-make is the problem. Even if you ONLY use mingw32-make it does not

[ros-dev] Problems with patchbot/newcc/rosbe

2012-03-05 Thread caemyr
After a quick look into your problems with patchbot it seems that vbox scripts were missing some errorlevel checks, which should bail out the test run at prepare stage when ISO was not present (which is the situation when you dont pass the proper revision/id number. Same thing was with newcc1

Re: [ros-dev] Problems with patchbot/newcc/rosbe

2012-03-05 Thread Zachary Gorden
Would also be nice if we could turn off the whole sound alert thing. Some of us find it a bit irritating. On Mon, Mar 5, 2012 at 6:11 PM, cae...@myopera.com wrote: After a quick look into your problems with patchbot it seems that vbox scripts were missing some errorlevel checks, which should