Closed Bug 1280633 Opened 8 years ago Closed 6 years ago

Step timings (Mozharness) to determine where to optimize our end to end times

Categories

(Testing :: General, defect, P3)

Product:
Testing
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [metrics]) 

gps mainly cares about variances of test jobs.
Whiteboard: [metrics]
How do we go about this bug?
Should we dupe it against bug 1270276 ("Record mozharness step data in perfherder")?
mozharness step durations are available in activedata and can be queried like:

{
	"from":"task",
	"where":{"eq":{"state":"completed"}},
	"select":[
		"action.duration",
		"task.id",
		"action.timings.harness.step",
		"action.timings.harness.duration"
	]
}

Good enough? Is there anything else to do in this bug?
Flags: needinfo?(armenzg)
Priority: -- → P3
Let's just call it a day.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(armenzg)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.