Testing Graveyard
6 years ago
9 months ago


(Reporter: armenzg, Unassigned)





6 years ago
I would like us not to worry about PGO at all.

The only place that I know that they are being displayed is:

Comment 1

6 years ago
I do not understand the purpose of this bug.  Can you elaborate on what contexts these should be ignored?  Only in buildcharts for gofaster?

Comment 2

6 years ago
I only saw it on the buildcharts.
I think it's ok to keep track of PGO builds, but we should probably be marking those that are included in the E2E time calculations explicitly. Does this sound like an ok compromise Armen?

Comment 4

6 years ago
Oh I think I understand something new. Please correct me if I am wrong.
In buildcharts, we don't mix PGO with non-PGO.

For instance for revision abdbf0646a21 I see two entries. The first one seems to be non-PGO jobs and the second one is PGO only:
  2.96 hours, started at 2011-10-29 16:54:15 last job: WINNT 5.2 leak test build
  3.73 hours, started at 2011-10-29 19:51:52 last job: WINNT 6.1 pgo test xpcshell

Is this correct? If so could we add some sort of way of making this obvious?

I was mainly wanted to make sure that apples and oranges were not mixed up. Sorry if I wasn't able to word it correctly.
Yup, it shouldn't be that hard to do so. I should be able to find an hour to do it today if it would be helpful.


9 months ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.