Closed
Bug 849701
Opened 11 years ago
Closed 11 years ago
Do periodic PGO on build-system
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: philor)
Details
Attachments
(1 file)
548 bytes,
patch
|
nthomas
:
review+
gps
:
feedback+
philor
:
checked-in+
|
Details | Diff | Splinter Review |
At the time of bug 729842, periodic PGO just kept running over and over on the tip, even if it had already run, which wasn't a good fit for b-s. Now, they are whining about not getting fast Windows builds. Once we give them periodic PGO, they'll merge things without waiting for PGO, and will then have to back out on m-c, but at least we won't have to listen to them whine about how slow their branch is, only about things that are their own fault.
Attachment #723313 -
Flags: review?(nthomas)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → philringnalda
Comment 1•11 years ago
|
||
Comment on attachment 723313 [details] [diff] [review] fix Is there someone who tends build system we can get confirmation/feedback from ?
Attachment #723313 -
Flags: review?(nthomas) → review+
Assignee | ||
Updated•11 years ago
|
Attachment #723313 -
Flags: feedback?(gps)
Comment 2•11 years ago
|
||
Comment on attachment 723313 [details] [diff] [review] fix Review of attachment 723313 [details] [diff] [review]: ----------------------------------------------------------------- This seems fine. We can always trigger a PGO if we need one sooner.
Attachment #723313 -
Flags: feedback?(gps) → feedback+
Assignee | ||
Comment 3•11 years ago
|
||
Comment on attachment 723313 [details] [diff] [review] fix http://hg.mozilla.org/build/buildbot-configs/rev/3cff563f36cf
Attachment #723313 -
Flags: checked-in+
Comment 4•11 years ago
|
||
This is in production.
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•