Open Bug 1418929 Opened 2 years ago Updated 2 years ago

g2/DAMP tests are not displayed on PerfHerder/compare page

Categories

(Tree Management :: Perfherder, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: ochameau, Unassigned)

References

Details

Component: Talos → Perfherder
Product: Testing → Tree Management
Version: unspecified → ---
Blocks: 1415532
this seems to be an issue with comparing to a branch, not a specific revision- more investigation is needed when I am at work in the morning.
I see more of the problem, what appears to happen here is that we have a default range of '2 days', and that applies to the age of the try push as well, not just the base branch (defaults to mozilla-central).

I think the fix here is to only apply the '2 days' to the base branch and show the results of a try push no matter what.  This seems valid as often we analyze a push from last week, rarely it seems that a push is >10 days old, typically 2-7 days old.
Last X days only applies for when you compare with a branch. I don't quite follow what it means to apply that to a given revision?

> I think the fix here is to only apply the '2 days' to the base branch and
> show the results of a try push no matter what.  

I agree with that sentence.

> This seems valid as often we analyze a push from last week, rarely it seems that a push is >10 days old,
> typically 2-7 days old.

But I don't quite follow this one (for the record, I original requested this special behavior in bug 1408912).
It can be very misleading to see the try results change depending on when you open it.
We can easily refer to a try push older than 10 days in bugs.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.