How feasible is to change the monobuild runner to attach gdb and dump all
threads before killing the hung up process?
This could be done manually by monitoring the buildbot. Most of us haven't
been able to reproduce this bug locally, so
squeezing some more usefull data from the buildbots is paramo
Rodrigo Kumpera wrote:
> How feasible is to change the monobuild runner to attach gdb and dump
> all threads before killing the hung up process?
>
> This could be done manually by monitoring the buildbot. Most of us
> haven't been able to reproduce this bug locally, so
> squeezing some more usef
Hi,
The failures are probably caused by errors in the tests themselves,
it should be enough
to run the tests with /labels to see what test is hanging.
Zoltan
On Tue, Nov 11, 2008 at 7:10 PM, Marc Christensen
<[EMAIL PROTECTED]> wrote:
> Rodrigo Kumpera wrote:
>> How feasible is to
Andrew added /labels to both trunk and branch system-2.0 unit test runs.
Once they rebuild, we should have this output.
Thanks for the suggestion,
Thomas
Zoltan Varga wrote:
> Hi,
>
> The failures are probably caused by errors in the tests themselves,
> it should be enough
> to run the tests
Thomas Wiest wrote:
> Andrew added /labels to both trunk and branch system-2.0 unit test runs.
>
> Once they rebuild, we should have this output.
>
Hmm, it doesn't look like the /labels helped:
http://build.mono.lab.novell.com/builds/HEAD/sles-10-i586/mono-branch/118545/logs/test-System-2.0.log
Thomas Wiest wrote:
> Thomas Wiest wrote:
>> Andrew added /labels to both trunk and branch system-2.0 unit test runs.
>>
>> Once they rebuild, we should have this output.
>>
> Hmm, it doesn't look like the /labels helped:
> http://build.mono.lab.novell.com/builds/HEAD/sles-10-i586/mono-branch/11
