Closed
Bug 494596
Opened 15 years ago
Closed 15 years ago
No l10n afterpush builds (since 05/11/09?)
Categories
(Mozilla Messaging Graveyard :: Server Operations, defect)
Mozilla Messaging Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stef, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4
Build Identifier:
We are no longer generating l10n afterpush thunderbird testing packages.
Don't know if it is related with bug 492985 but it has significant negative impact on our testing and qa process.
Reproducible: Always
Comment 1•15 years ago
|
||
What's afterpush?
Comment 2•15 years ago
|
||
(In reply to comment #1)
> What's afterpush?
I'll guess l10n repack builds triggered by a push to one of the l10n repositories.
If that's the case, I believe I found what the problem was (caused by the buildbot 0.7.10p1 upgrade) and applied a configuration update that should fix it.
Since I can't push to any l10n repositories to test this, I'll wait for confirmation that it's working before closing this and pushing the required buildbot master configuration change.
Reporter | ||
Comment 3•15 years ago
|
||
(In reply to comment #2)
> (In reply to comment #1)
> > What's afterpush?
>
> I'll guess l10n repack builds triggered by a push to one of the l10n
> repositories.
Exactly.
> Since I can't push to any l10n repositories to test this, I'll wait for
> confirmation that it's working before closing this and pushing the required
> buildbot master configuration change.
Within an hour after http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pl/rev/650/ there was no tb build (http://tinderbox.mozilla.org/Mozilla-l10n-pl/).
Comment 4•15 years ago
|
||
As of Mon 25 May 2009 00:40:48 EDT, I've applied a different possible fix to the buildbot master, awaiting next l10n push.
Reporter | ||
Comment 5•15 years ago
|
||
Works! :-)
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•