Closed Bug 850476 Opened 8 years ago Closed 6 years ago

B2G FPS test reports data in fps not milliseconds

Categories

(Datazilla Graveyard :: User interface, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cmtalbert, Unassigned)

Details

(Keywords: ateam-datazilla-task, perf, Whiteboard: [c=automation p= s= u=])

The labels of the y axis in the fps test on datazilla are incorrect. The fps test is reporting frames per second, not milliseconds. We might want to make the y axis unit label part of the datazilla input json? Then it could default to milliseconds as it does now if that attribute is not present, but if it is we could then use whatever label the test sends in? Unfortunately, I'm not sure how to do that with our schema though.

Alternatively, if it is easier, I'm totally happy hardcoding the labels for the fps test to 'fps'.  Whichever is faster and easier. I don't imagine there will be a huge need for different units on the fly within the b2g tests, but I can't really say what will be thrown at datazilla next.
Priority: -- → P2
Keywords: perf
Whiteboard: [c=automation p= s= u=]
Datazilla is being deprecated this quarter.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.