Seamonkey (trunk) not being built anymore since 2008-11-01 except on Windows

VERIFIED FIXED

Status

SeaMonkey
Build Config
--
major
VERIFIED FIXED
10 years ago
10 years ago

People

(Reporter: tonymec, Assigned: Robert Kaiser)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Severity: critical → major
These machines are maintained by KaiRo et al, and don't fall into IT's realm of support. I also don't think it's anything to do with bug 398148 - the permissions look fine. It's just no builders means no builds.
Assignee: server-ops → build-config
Component: Server Operations: Tinderbox Maintenance → Build Config
Product: mozilla.org → SeaMonkey
QA Contact: mrz → build-config
Version: other → unspecified
I mentioned bug 398148 because the fact that it happened on the first of a month, and on all platforms but one, looked suspicious to me. Better mention an irrelevant bug than miss an essential one.
I've just taken a look, but this look like it needs KaiRo or Callek to poke the buildbots on those machines.
Version: unspecified → Trunk
(Assignee)

Comment 4

10 years ago
Both boxes seemed to have timed out during a hg update and then refused to start new builds. I have restarted the slaves on both machines, builds should be coming back now.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Assignee)

Updated

10 years ago
Assignee: build-config → kairo
Maybe trigger an out-of-turn nightly?
OK, three Linux hourlies (!) have been built by now and a nightly is in the works. For the Mac it has started but not as fast. I'll VERIFY when I see all 4 kinds of build (hourly & nightly for Linux & Mac) on the FTP server. :-)
Hm, looks OK for Linux, but for the Mac (after 4 "hourlies"), it apparently still hasn't noticed that the latest nightly was more than two and a half days old. We'll see if the Mac nightly gets built at it usual time tomorrow.
Apparently the buildbot read my mind. All 4 kinds of builds have been uploaded => VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.