Closed Bug 692370 Opened 13 years ago Closed 13 years ago

PGO builds don't appear in self-serve under the rev

Categories

(Release Engineering :: General, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: catlee)

References

Details

(Whiteboard: [pgo][cleanup])

Attachments

(1 file)

I was going to say of bug 692301 that it wasn't quite critical severity, since like most tbpl bobbles you could just look in self-serve to see what the status of the build was, and look at the log on stage if it wasn't green, but as https://build.mozilla.org/buildapi/self-serve/mozilla-central/rev/4a69b3fdd602 says, "pgo build? what pgo build? got some tests, but no build."
Assignee: nobody → catlee
Priority: -- → P1
So the problem here looks like the PGO builds aren't getting triggered with a branch set in their sourcestamp. Looking at the scheduling code now.
The pgo build scheduler is missing a branch setting; patch coming shortly.
Attachment #565222 - Flags: review?(bhearsum)
Attachment #565222 - Flags: review?(bhearsum) → review+
Attachment #565222 - Flags: checked-in+
Flags: needs-reconfig?
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: needs-reconfig?
Resolution: --- → FIXED
I hate to be a greedy pest, but as that link says, revision: null, and while it's nice that https://build.mozilla.org/buildapi/self-serve/mozilla-central with "pgo-build" in the filter shows lots of pgo-builds, all with empty revisions, what I actually mean when I say self-serve is "the Win PGO build in https://tbpl.mozilla.org/?tree=Mozilla-Aurora&rev=c0c7322521b7 is hosed, I want to either click tbpl's rebuild button, or the link to https://build.mozilla.org/buildapi/self-serve/mozilla-aurora/rev/c0c7322521b7 and be able to retrigger it there, but since there's no rev, there's no /rev/ and tbpl's rebuild request just fails with '(could not find build)'."
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
So, I'm not sure how TBPL is finding the jobs in self-serve, but I'm going to say this is blocked by 691675, since the implementation of that will most likely provide a revision via the scheduler, which will then be exposed via self-serve.
Blocks: pgo-improvements
No longer blocks: 658313
Depends on: 691675
Priority: P1 → P3
tbpl finds them on the floor of a hotdog factory, in http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/tip/js/MachineResult.js#l115 where it looks for the buildid of the first build of the same type on that rev, so it does the same thing I do, opens the self-serve page for that rev and scans for "pgo-build".
Summary: PGO builds don't appear in self-serve → PGO builds don't appear in self-serve under the rev
A revision would certainly be nice, since when we had the PGO-only regression that we never have, never having them being the reason we could get away with periodic PGO, I thought I was being all cunning by using https://build.mozilla.org/buildapi/self-serve/mozilla-inbound instead of the rev URL, to find and retrigger the PGO build, but of course without a revision it's not a retrigger, it's a "create a brand new build on whatever happens to be tip right now."
over to jhford to get the scheduling fixed (we need to schedule the jobs with an actual revision in the sourcestamp)
Assignee: catlee → jhford
I am putting this bug back in the pool. I am also unsure how to do this
Assignee: jhford → nobody
Whiteboard: [triagefollowup]
Component: Release Engineering → Release Engineering: Developer Tools
Priority: P3 → --
QA Contact: release → lsblakk
Whiteboard: [triagefollowup] → [pgo][cleanup]
Fixed by bug 691675.
Assignee: nobody → catlee
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: