Closed
Bug 596388
Opened 14 years ago
Closed 14 years ago
No Firefox builds on http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-af&hours=72 etc for 3 days
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: catlee)
References
()
Details
Attachments
(1 file)
4.34 KB,
patch
|
nthomas
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
There are no Firefox builds reported to the per-locale tinderbox pages. http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-af&hours=72 is not showing any, while http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n&hours=72 does, same for de, at least.
This blocks me from checking that we actually have successful builds for new locales on Firefox 4 Beta 7.
Comment 1•14 years ago
|
||
Looking at the admin pages for a couple of individual locales I don't think we are reporting any Firefox l10n build unto those pages.
We seem to still have that code in place for buildbot-0.8.0:
http://hg.mozilla.org/build/buildbotcustom/file/buildbot-0.8.0/misc.py#l666
and the only difference that I see with the default branch:
http://hg.mozilla.org/build/buildbotcustom/file/default/misc.py#l1189
is the from address.
The other differences I see are:
* if config['enable_l10n_onchange']:
* nomergeBuilders.extend(l10n_builders)
I see the code enabling the l10n on change:
* mozilla/config.py:BRANCHES['mozilla-central']['enable_l10n_onchange'] = True
I ain't got time as of now but I thought this info could help. I don't see at first anything that got lost when porting to 0.8.0 masters.
Reporter | ||
Comment 2•14 years ago
|
||
I think this worked in post 0.8.0 era times, too. Seems like a really recent regression.
Regression range is between http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-af&maxdate=1283015590&hours=72&legend=0&norules=1 and http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-af&maxdate=1283274790&hours=72&legend=0&norules=1, likely post 2010/08/28.
Comment 3•14 years ago
|
||
Maybe?
* Bug 589765: Set treeStableTimer=None for l10n repack jobs. - http://hg.mozilla.org/build/buildbotcustom/rev/30499aa7f126
* Bug 559150: Don't use hard coded values for pollInterval and l10nPollInterval. - http://hg.mozilla.org/build/buildbotcustom/rev/770d99c11673
From looking at commit messages on the 0.8.0 branch.
I so wish we had a unit test for this and when the repacks don't trigger on-change as it takes long to notice.
Reporter | ||
Comment 4•14 years ago
|
||
So the problem is that TinderboxMailNotifier doesn't support WithProperties for tree. No wonder if or why that regressed.
Assignee | ||
Comment 5•14 years ago
|
||
Most likely got lost in the 0.8.1 upgrade.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → catlee
Priority: -- → P2
Assignee | ||
Comment 6•14 years ago
|
||
Attachment #475639 -
Flags: review?(nrthomas)
Updated•14 years ago
|
Attachment #475639 -
Flags: review?(nrthomas) → review+
Assignee | ||
Updated•14 years ago
|
Blocks: releng-downtime
Assignee | ||
Updated•14 years ago
|
Flags: needs-treeclosure+
Assignee | ||
Updated•14 years ago
|
Flags: needs-treeclosure+ → needs-treeclosure?
Comment 8•14 years ago
|
||
These appear to be working again.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 9•14 years ago
|
||
Comment on attachment 475639 [details] [diff] [review]
Re-import upstream's tinderbox.py
Landed in 69c9e45f48e3
Attachment #475639 -
Flags: checked-in+
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•