Closed Bug 760373 Opened 13 years ago Closed 13 years ago

We aren't building PGO on the mozilla-release tree

Categories

(Release Engineering :: General, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: philor)

Details

Attachments

(1 file)

I was enjoying the lovely sight of all the green on https://tbpl.mozilla.org/?tree=Mozilla-Release, when I realized that it being competely green was a sign of a horrible bug, because 13 is on it now, and 13 is permaorange on Linux64 PGO mochitest-other. We're not testing what we ship, which is not a good state to be in (though it is true that we've apparently gotten away with it since... forever).
Attached patch fixSplinter Review
Someday, I should really learn what the difference between mozilla/config.py and mozilla-tests/config.py is, other than the apparent difference here, that the hunk in http://mxr.mozilla.org/build/source/buildbot-configs/mozilla-tests/config.py#1057 does nothing, while the ones for aurora and beta in mozilla/config.py actually do something.
Assignee: nobody → philringnalda
Status: NEW → ASSIGNED
Attachment #629083 - Flags: review?(catlee)
Attachment #629083 - Flags: review?(catlee) → review+
Is there any remaining work in this bug? Or are we just waiting to verify?
I don't think this has been deployed yet.
This went went into production today.
Got a push, built PGO, got the permaorange test we should have gotten.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: