Closed Bug 1316856 Opened 9 years ago Closed 8 years ago

L10n Aurora Nightlys should use the rev specific for pulling and not something else

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: cbook, Unassigned)

Details

We had today aurora l10n nightly bustage like https://treeherder.mozilla.org/logviewer.html#?job_id=4124707&repo=mozilla-aurora This bustage ( 03:49:56 INFO - 0:31.74 Test manifest (/builds/slave/m-aurora-l64-l10n-ntly-2-00000/build/mozilla-aurora/dom/security/test/csp/mochitest.ini) lists test that does not exist: test_bug1312272.html) was caused by the landing of https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora&revision=deaa7a4a8cd37e9d482f7df37ffcc48ae215d722 however, the nightly builds were triggered for rev https://hg.mozilla.org/releases/mozilla-aurora/rev/94d52b7d3d048a05f67f2c3c1736e4f1bdf5eee3 which landed 6 hours before the bustage checkin happened. So the Nightly Builds were pulling something from a cset that was not the specific changeset (94d52b7d3d048a05f67f2c3c1736e4f1bdf5eee3) for the build of the nightly builds. I guess we should only pull & build for the revision that was requested for nightly builds and not from something later.
btw and retriggered l10n nightly builds after i fixed the bustage and that also fixed the broken nightlys
I think this is a dupe of bug 1250626 ?
Component: General Automation → General
I think this bug outlived its usefulness. Closing this, feel free to reopen if I'm wrong.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.