Closed Bug 515330 Opened 15 years ago Closed 15 years ago

Mac l10n nightly builds for Thunderbird are out of date (last update Sep 2 2009)

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 515360

People

(Reporter: flod, Assigned: gozer)

References

()

Details

While other builds (Win and Linux) are updated, most of Mac builds for Thunderbird are more than one week old (September, 2th 2009). This happens both on latest-comm-central-l10n and latest-comm-1.9.1-l10n.
Thanks for the report. Both trunk + Branch builders have 108 builds pending on nightlies - this would be 2 sets worth of nightly builds queued. de has had a build on 1.9.1 on the 6th - that appears to be the most recent build on that branch (and it wasn't a nightly). The latest 1.9.1 nightlies were done on the 2nd, the latest trunk nightlies were on the 6th. So the dates of buildbot versus ftp tie up, so I don't think there is a config error. The only thing I see is that the momo-vm-osx-leopard-04 is stuck on a build from the 6th. I guess this could be confusing the scheduler. I've tried to gracefully shut it down, it might free up the scheduler but I doubt it. In any case, assigning to our build guy who should be able to poke around a bit more. Having one builder down isn't good, but we could also just be behind on doing builds anyway (on mac).
Assignee: nobody → gozer
I've killed off today's Mac shark nightly build as well in the hopes that it frees up another builder for a few hours (hence if it isn't the scheduler at fault, we may have a slightly better chance of getting to the l10n builds).
Thanks Mark for the quick reaction, we're approaching the string freeze and Mac builds are always a pain to check ;-)
(In reply to comment #1) > Thanks for the report. > > Both trunk + Branch builders have 108 builds pending on nightlies - this would > be 2 sets worth of nightly builds queued. > > de has had a build on 1.9.1 on the 6th - that appears to be the most recent > build on that branch (and it wasn't a nightly). So that build was triggered by a l10n change > The latest 1.9.1 nightlies were done on the 2nd, the latest trunk nightlies > were on the 6th. So the dates of buildbot versus ftp tie up, so I don't think > there is a config error. Buildbot died at least once after the 2nd, so that would have taken down with it the pending l10n jobs. > The only thing I see is that the momo-vm-osx-leopard-04 is stuck on a build > from the 6th. I guess this could be confusing the scheduler. Yes, that's quite interestingly bad. And my monitoring didn't notice, since from buildbot's point of view, the builder was up and running, annoying. > I've tried to gracefully shut it down, it might free up the scheduler but I > doubt it. It's so stuck it didn't even shutdown, so I had to reboot it. > In any case, assigning to our build guy who should be able to poke around a bit > more. Having one builder down isn't good, but we could also just be behind on > doing builds anyway (on mac). Hopefully, once the stuck builder comes back, things should speed up again some.
Blocks: 470669
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.