Closed
Bug 467649
Opened 16 years ago
Closed 16 years ago
The l10n scheduler's name when declaring DependentL10n is incorrect
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: coop)
References
Details
Attachments
(1 file)
1.64 KB,
patch
|
coop
:
review+
coop
:
checked-in+
|
Details | Diff | Splinter Review |
There are discrepancies between what gets added to l10nNightlyBuilder, the patch fixes this: Old code: c['schedulers'].append(DependentL10n( name='%s l10n' % sched, New code: c['schedulers'].append(DependentL10n( name=l10nNightlyBuilders[i], By using this in master.cfg: log.msg(l10nNightlyBuilders[i]) log.msg(sched + 'l10n') #This is the same as '%s l10n' % sched I would get this in twistd.log: Linux mozilla-central l10n nightly Linux mozilla-central nightly l10n
Attachment #351069 -
Flags: review?(ccooper)
Assignee | ||
Updated•16 years ago
|
Attachment #351069 -
Flags: review?(ccooper) → review+
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → ccooper
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Updated•16 years ago
|
Attachment #351069 -
Flags: checked‑in+
Assignee | ||
Comment 1•16 years ago
|
||
Comment on attachment 351069 [details] [diff] [review] fixes the name given to a DependentL10n scheduler changeset: 580:087a643f7707
Reporter | ||
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•16 years ago
|
||
The first set of dependent l10n builds trigger correctly after a mozilla-central en-US nightly, but subsequent nightlies do not seem to trigger the dependent scheduler. Armen has posited that there may be a discrepancy between the builder names between various parts of the scheduling process: http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/master.cfg#l74 http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/master.cfg#l168
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•16 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 3•16 years ago
|
||
A master restart seems to have resolved this.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
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
•