Closed Bug 1132697 Opened 10 years ago Closed 6 years ago

Add visual markers for the performance events

Categories

(Firefox OS Graveyard :: Developer Tools, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: ikumar, Unassigned)

References

Details

(Whiteboard: [caf priority: p2][CR 798546])

During offline discussions it came out that it will be good to have visual markers for the performance events e.g., visually loaded, fully loaded etc so that high speed camera based performance measurements could be compared with the logcat based measurements using the events.

These markers could be enabled either compile time (debug flags) or run time (hot key sequence).
blocking-b2g: --- → 2.2?
Triage is not blocking as this seems more like a feature request.
blocking-b2g: 2.2? → ---
Whiteboard: [CR 798546]
Whiteboard: [CR 798546] → [caf priority: p2][CR 798546]
[Blocking Requested - why for this release]:

This is required for CAF and Mozilla to compare automated and manual High-speed Camera Performance test results. We agreed not to block on this for 2.2 due to timeline restraints but will need this addressed for 3.0.
blocking-b2g: --- → 3.0?
I believe the solution to this will be to pop up a small box on the screen with the name of the performance marker that was generated. Since this is not a Raptor detail, forwarding.
Component: Gaia::PerformanceTest → Developer Tools
No longer blocks: CAF-v3.0-FL-metabug
No longer blocks: CAF-v2.2-metabug
No longer blocks: CAF-v2.2-metabug
Hey Inder, 

Is this something required as part of our 2.5 release? Thanks
Flags: needinfo?(ikumar)
Wilfred, is this a requirement for 2.5?
Flags: needinfo?(wmathanaraj)
[Triage] We won't be blocked by this.
blocking-b2g: 2.5? → -
Depends on: 1189613
Flags: needinfo?(wmathanaraj) → needinfo?(ffos-product)
Priority: -- → P2
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Flags: needinfo?(ikumar)
Flags: needinfo?(ffos-product)
You need to log in before you can comment on or make changes to this bug.