Closed Bug 1253218 Opened 9 years ago Closed 5 years ago

when using compare view in perfherder it is unclear that the base revision needs retriggered jobs

Categories

(Tree Management :: Perfherder, enhancement, P3)

Product:
Tree Management
Component:
Perfherder
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: jmaher, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: perfherder-docs)

perfherder compare mentions it needs more data, but it isn't clear on what that really means and how to do it. It makes sense to retrigger or get more data for your try push, but the base revision that you compare to (many times on m-c) needs more data and that part is easy to get confused. This could be a simple text change in the UI- maybe a more comprehensive docs section as well.
Whiteboard: perfherder-docs
Priority: -- → P5
See Also: → 1484714
No longer blocks: 1565516
Blocks: 1202718
No longer blocks: 1202718
Depends on: 1202718
Type: defect → enhancement
Blocks: 1565516

perfherder compare mentions it needs more data, but it isn't clear on what that really means and how to do it.

This bug requires the 'Retrigger' button from bug 1202718 & its functionality. It will address the above issue nicely.

What's left here is decide on a better definition of the docs.

  • do we need more than one?
  • if yes, where should we place them?
Blocks: 1570944
No longer blocks: 1568462
No longer blocks: 1570944
Priority: P5 → P3

This ticket is much older than 18 months, thus closing it as INCOMPLETE.

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