Closed Bug 1322853 Opened 8 years ago Closed 8 years ago

Use a common, monotonically increasing timestamp for Autophone perf tests

Categories

(Firefox for Android Graveyard :: Testing, defect, P2)

Product:
Firefox for Android Graveyard
Component:
Testing
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: snorp, Assigned: snorp)

References

Details

(Whiteboard: [fixed by Bug 1359176])

Right now we use the logcat time, which is not great because of clock skew. We should use whatever monotonically increasing clock source we can share between Java and Gecko (both native + js). We should take this opportunity to also add some more useful data points. I think the list is something like: 1) App start 2) Page load start 3) First paint 4) Interactive document state 5) Page load stop
Assignee: nobody → snorp
Priority: -- → P2
Fixed by Bug 1359176
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by Bug 1359176]
I may have been premature in closing this. Snorp, if we still want to add the additional data please reopen.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.