700924 - On branches with only PGO builds, add "PGO" to the build name

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Phil Ringnalda (:philor)]

Or, the other alternative that would also work for tbpl, put pgo in the build names.

If you look at tbpl for mozilla-beta or mozilla-aurora, you'll see right away that something must be badly broken, because the Linux and Linux64 and Windows opt builds completed, but there are no tests on the row after them. Given enough time, and enough memory of every releng bug that has been fixed in the last few weeks, you might remember that they only do PGO builds again, and the tests on a row marked PGO because the tests have it in their name match up with the builds on a row not marked PGO because the builds don't have it in their name even though they did build PGO.

Comment 1

[Chris Cooper [:coop] (he/him)]

Yes, some standardization would be good here. Myself, I'd rather have the builds also explicitly marked as PGO rather than need to remember which branch I'm looking at.

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

putting back into the pool.  I haven't had a chance to dig into this yet.

Comment 4

[[e-mail] (:bhearsum)]

Is this still an issue in the current state of PGO?

Comment 5

[Phil Ringnalda (:philor)]

It is, yes.

Comment 6

[[e-mail] (:bhearsum)]

I'm going to optimistically close this on the assumption that everything is well in the treeherder+taskcluster world.