Closed Bug 725214 Opened 14 years ago Closed 14 years ago

Bug 698827 avoided doing 10.5 debug builds on 10.6 on aurora and beta, but forgot about release and esr10

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: armenzg)

References

Details

(Keywords: regression)

Attachments

(1 file)

(Well, I'm not sure esr10 existed at the time, but it does now.) Bug 698827 very carefully avoided switching the 10.5 debug builds to running on the 10.6 slaves on aurora or beta until 12.0 merged into those trees, because there's code changes in 12.0 that using 10.6 to do the 10.5 builds depend on. It didn't, however, do anything to avoid building 10.5 debug on 10.6 in mozilla-release, or in mozilla-esr10, as the timed-out "10.5" debug build on mozilla-release in https://tbpl.mozilla.org/php/getParsedLog.php?id=9170653&tree=Mozilla-Release which was done on moz2-darwin10-slave41 shows.
Blocker both because it's my favorite severity, and because this is currently blocking the go to build for the 10.0.1 chemspill, since that failure is on the tip of mozilla-release, though retriggering will probably luck us into a build that will manage not to hang before a patch and a reconfig get us back to using the right slaves.
Assignee: nobody → armenzg
Attachment #595494 - Flags: review?(coop) → review+
It does not block a release. Reducing severiting.
Severity: blocker → major
Attachment #595494 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: