Closed Bug 1329240 Opened 3 years ago Closed 2 days ago

Add a link to the pushlog for the visible changeset range

Categories

(Tree Management :: Perfherder, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ted, Unassigned)

Details

I find myself occasionally looking at a perfherder graph that shows an improvement or regression, but it's not immediately obvious what caused it, like:
https://mzl.la/2jbXc0S

I tried clicking on a few data points to look at the pushlog, but nothing stood out. I'd love to have a link to the pushlog for all changesets in the visible range, so that I could zoom in a bit and just click through to see everything in that range.
We could probably just dump this information on the bottom of the graph. E.g.:

Visible revision range: ABCD1234 -> EFGH5678

The one complication with implementing this is that multiple ranges are possible for the cases we're showing series from multiple branches. So maybe we'd do:

Visible revision range: mozilla-inbound ABCD1234 -> EFGH5678
Visible revision range: autoland IJKL9101 MNOP1121
Type: defect → enhancement

Dave, what do you think of a feature like this? For one, I think it aligns with the Perfherder-enhanced Hg view we talked about once.

Basically, a Perf sheriff zooms into a noisy section, gets perplexed. Then jumps to the Hg view; maybe Perfherder could hint him some likely suspects.

(I haven't yet filed a bug for that Perfherder-enhanced Hg view.)

Flags: needinfo?(dave.hunt)

I imagine linking to the range would be easier that integrating a commits view into Perfherder, so I think this is a good idea to keep.

Flags: needinfo?(dave.hunt)

(In reply to Dave Hunt [:davehunt] [he/him] ⌚BST from comment #3)

I imagine linking to the range would be easier that integrating a commits view into Perfherder, so I think this is a good idea to keep.

Jotted this down into our internal roadmaps.
Given that this ticket is much older than 18 months, I'm closing it as INCOMPLETE.

Status: NEW → RESOLVED
Closed: 2 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.