2. BuildBot can't cope with dropped connections in the middle of a build. Again I have a ticket open against BuildBot but fixing it apparently requires large amounts of infrastructure refactoring, so it's currently scheduled for the next-but-one major release of BuildBot, which could be months or years away.
at least it has "major" priority.. http://buildbot.net/trac/ticket/25
I'm not familiar with buildbot internals, but would it be possible to work around this by turning a continuous "build" task into two tasks - "start a build" and "report any build results" (with the build running unconnected in between, and the "report" task simply collecting any and all reports that have piled up locally)? Claus _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
