[Mono-devel-list] Buildbot test passage status

Ben Maurer bmaurer at ximian.com
Wed Feb 16 10:15:57 EST 2005

Hey guys,

Now that the corlib tets are passing (for the most part), I have been
doing a bit of work on getting buildbot to run them. I think we are
really close to getting a green tree.

Martin fixed one of the biggest problems we had (the --debug regression

Right now, here are the issues that I am seeing:

All Platforms

--- Remoting tests are failing, with, eg,
1) MonoTests.Remoting.HttpSyncCallTest.TestInstanceSimple : Channel not

I filed a bug for lluis on this.

--- Timeouts of aborts of AD threads
This is a warning, but it doesn't sound good:
** (../../class/lib/default/nunit-console.exe:26465): WARNING **:
Aborting of threads in domain
domain-System.Runtime.Remoting_test_default.dll timed out.

--- 2.0 nunit tests hang

I've yet to run teh 2.0 nunit tests successuflly. On buildbot I am

/home/builder/HEAD/mono/runtime/mono-wrapper --debug
/exclude:NotWorking,ValueAdd,CAS,InetAccess /xml:TestResult-net_2_0.xml
corlib_test_net_2_0.dll || ok=false; \ sed '1,/^Tests run: /d'
TestResult-net_2_0.log; \

command timed out: 1200 seconds without output, killing pid 2934
process killed by signal 9
program finished with exit code -1

Also note the high number of failures on the 2.0 nunit tests.

I have to look at what tests are hanging here, though I'd apprecitate
some help.


I see this error, which does not pop up on x86:
1) MonoTests.System.IO.FileStreamTest.Constructor_InvalidFileHandle :
Expected: ArgumentException but was IOException

in [0x000e5] System.IO.FileStream:.ctor

I'll file a bug.

The verification step fails with:

The assembly mscorlib.dll was not found or could not be loaded.

It should have been installed in the
`c:\buildbot\HEAD\mono\mono\lib\mono\1.0\mscorlib.dll' directory.

This sounds like a setup problem.

The build fails with
configure: running /bin/sh ./configure --prefix=/mono 
'--enable-maintainer-mode' '--enable-compile-warnings'
'--with-preview=yes' '--prefix=/mono' --disable-embed-check
--with-libgc-threads=pthreads --cache-file=/dev/null --srcdir=.
./configure: ./configure: No such file or directory
configure: error: /bin/sh ./configure failed for libgc

I don't know what happens with tests


Tons of errors on test, most common is:

/export/home/builder/HEAD/mono/runtime/mono-wrapper --debug -O=-all
Exit code: 138
Bus Error - core dumped

More information about the Mono-devel-list mailing list