On its build of Jan 08 07:24, "MacOSX 10.4 comm-central-calendar ltn nightly" lost its connection to the slave, for some reason it hasn't built since (though the dep builder has).
restarted buildbot slave on that host, should probably fix it. The buildbot master restarted a few times recently, and sometimes, as a result, clients get confused.
In this case, the usual thing to do would have been to respin the nightly by telling the irc bot (sunbuild) to respin. Note the dep/nightly builders are one and the same buildbot builder/host, just different configurations to build.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(In reply to comment #2) > In this case, the usual thing to do would have been to respin the nightly by > telling the irc bot (sunbuild) to respin. I didn't do that as the buildbot master said there was already a build pending, but it just wasn't kicking it off.
Sadly, no new builds have appeared since the 7th. Furthermore, attempting to look at buildbot yields the following error: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /buildbot/production/waterfall. Reason: Error reading from remote server Apache/2.2.3 (CentOS) Server at build.mozillamessaging.com Port 80 The bot that I see in #calendar seems to be called calbuild rather than sunbuild, and telling it "respin" in a /msg doesn't seem to cause anything to happen. Suggestions?
Severity: normal → critical
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
It appears all the Sunbird mac machines are broken. I've poked them a couple of times with clobbers, but I've got no idea what is happening. cc'ing ause as he may know/have access to them.
last command shown in the logs (hdutil) seems to run successful. the expected output (hybrid.dmg) exists. the twisted.log shows ------- ... 2009/01/13 03:12 PST [-] command timed out: 1200 seconds without output, killing pid 5609 2009/01/13 03:12 PST [-] trying os.kill(-pid, 9) 2009/01/13 03:12 PST [-] signal 9 sent successfully 2009/01/13 03:12 PST [-] Traceback (most recent call last): ... ------- so it might be a simple timeout issue that probably have to be handled on the bot master.
found a hanging launchd eating up cpu time. rebooting the machine and starting the bot from the gui gave me gree builds again.
all builds green
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.