perfherder compare is very limited when developers are investigating a regression or making their test relevant or stable
Categories
(Tree Management :: Perfherder, task, P3)
Tracking
(Not tracked)
People
(Reporter: jmaher, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: student-project)
Reporter | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Comment 5•5 years ago
|
||
Hi saijatin28, thanks for your interest in working on this.
first thing is to setup a development environment for perfherder:
https://github.com/mozilla/treeherder/
I feel that this work item is slightly ambiguous and maybe not the best work item to tackle for one of the first couple bugs related to perfherder- I do think it is a great project to work on as it can shed light on many things and will be very useful to implement.
:igoldan, can you help add more detail here related to how specifically we would implement this, what data we would use, where it would go in the current UI, what controls might be needed? Also if there is related work that is planned which could yield bitrot or conflicts with the compare view.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
We weren't able to get to this in Q3, and have already planned Q4 work. Removing this from blocking the Q3/2019 meta bug so we can consider this for 2020.
Description
•