I already alerted gmcdonald to that. Not sure what the underlying cause is, but its happened before.
On Wed, May 5, 2010 at 7:17 AM, Adam Kocoloski <kocol...@apache.org> wrote: > Thanks Paul, I tried that, but it looks like the buildbot failed to clean up > after itself from the previous attempt: > > http://ci.apache.org/builders/couchdb-trunk/builds/308/steps/svn/logs/stdio > > What's the next step? > > On May 4, 2010, at 10:59 PM, Paul Davis wrote: > >> Theoretically, on IRC, its: >> >> couchbot: force build ${BUILDER} >> >> Where ${BUILDER} can currently be couch-trunk or couch-cover. >> >> I know of spurious errors when both builds run at the same time due to >> our tests not using random ports when we start a full server. (Both >> try and grab port 5984, one fails) >> >> Though currently, couchbot has gone missing. I think there's an email >> endpoint but I don't know it off the top of my head. >> >> HTH, >> Paul Davis >> >> On Tue, May 4, 2010 at 10:10 PM, Adam Kocoloski <kocol...@apache.org> wrote: >>> How do I force another build? I can't reproduce the test failure locally. >>> >>> Adam >>> >>> On May 4, 2010, at 4:59 PM, build...@apache.org wrote: >>> >>>> The Buildbot has detected a new failure of couchdb-trunk on ASF Buildbot. >>>> Full details are available at: >>>> http://ci.apache.org/builders/couchdb-trunk/builds/306 >>>> >>>> Buildbot URL: http://ci.apache.org/ >>>> >>>> Buildslave for this Build: bb-vm_ubuntu >>>> >>>> Build Reason: >>>> Build Source Stamp: [branch couchdb/trunk] 941033 >>>> Blamelist: kocolosk >>>> >>>> BUILD FAILED: failed compile_5 >>>> >>>> sincerely, >>>> -The ASF Buildbot >>>> >>> >>> > >
