Karel Gardas <[email protected]> writes: > In fact you have made that advice to me already in the past and I > followed it. I repeated the testing again and the problem is that (like > in the past): Oh drat. I must have forgotten about that.
> ghc --make Setup > ./Setup test > > runs fine on my OpenBSD bot. Shall I test several times? Or do you have > any other idea what to test? If you feel adventurous, one option would be to move the buildbot to the new buildmaster, and point it to a different darcs repository/branch (one under your control). That would allow you to inject patches into your buildbot without external intervention. (It needs to move to the new buildmaster because we can't directly change the configuration of the old one.) That would then let you record a patch that removes part of the tests and hit force rebuild to see if that helped, eg.. You could also add some debugging statements to Distribution/ShellHarness.hs to see what's going on. And we could also modify the buildmaster to run the testsuite in some sort of debugger -- is valgrind available on your machine? Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
