Closed
Bug 427425
Opened 16 years ago
Closed 16 years ago
WINNT 5.2 l10n-win32-tbox, l10n windows tinderbox hung
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: chizu)
Details
Attachments
(1 file)
36.08 KB,
text/plain
|
Details |
The l10n windows firefox tinderbox seems to be hung again. This seems to happen every other day right now, there's at least bug 427197, and localizers report more occurances. CCing beltzner and schrep in case this turns into a Firefox 3 RC 1 risk. I see two issues at hand, - we need l10n builds now, we're expecting l10n to sign off 'til Tuesday, testing is their top priority, - an idea why that happens so often these days, I dont't think we want to go into an RC1 with a tinderbox that throws dices if it completes the build or not.
Comment 1•16 years ago
|
||
(In reply to comment #0) > The l10n windows firefox tinderbox seems to be hung again. > > This seems to happen every other day right now, there's at least bug 427197, > and localizers report more occurances. Bug 425903 and Bug 426502 too, CCing nthomas
Comment 2•16 years ago
|
||
Axel, can you spot anything unusual in this ?
Updated•16 years ago
|
Attachment #313975 -
Attachment description: log for the locale that build died one → log for the locale build that died
Reporter | ||
Comment 4•16 years ago
|
||
I don't see anything obvious. I did a massive landing for slovene on 2008-04-04 03:45, but that's really just merging the branch over to the trunk. The output changed, but it should have become smaller, I'd think. Bug 425903 seems to predate that check-in, though. Do we know if it's always the same locale breaking?
Comment 5•16 years ago
|
||
Thanks Trevor, we'll debug this somewhere outside your queue (bug 402339).
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•