Closed
Bug 856512
Opened 12 years ago
Closed 12 years ago
[FHR] How is the time open computed
Categories
(Firefox Health Report Graveyard :: Web: Health Report, defect)
Firefox Health Report Graveyard
Web: Health Report
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: joy, Unassigned)
Details
How is
a) vital stats --> time open (mine = 3072 mins)
b) this month --> time open (mine=28 mins)
computed?
None of the ways i computed
- summing org.mozilla.appSessions.previous$cleanActiveTicks*5/60 mins
- summing org.mozilla.appSessions.previous$cleanTotalTime/60 mins
But none match. Moreover, I live in San Francisco and the time is 10:20 pm, March 31st. However, i have April 1st in my days fields(no jokes!). Does this mean "This month" is April?
Comment 1•12 years ago
|
||
(In reply to Saptarshi Guha from comment #0)
> How is
>
> a) vital stats --> time open (mine = 3072 mins)
> b) this month --> time open (mine=28 mins)
>
> computed?
> None of the ways i computed
>
> - summing org.mozilla.appSessions.previous$cleanActiveTicks*5/60 mins
> - summing org.mozilla.appSessions.previous$cleanTotalTime/60 mins
>
The calculation is in this function:
https://github.com/mozilla/fhr-jelly/blob/master/js/data.js#L31
As you can see it's the cleanTotalTime + abortedTotalTime for the period.
> But none match. Moreover, I live in San Francisco and the time is 10:20 pm,
> March 31st. However, i have April 1st in my days fields(no jokes!). Does
> this mean "This month" is April?
I would guess the FHR data service uses UTC. deinspanjer may be able to comment further.
Comment 2•12 years ago
|
||
Yes, all dates in FHR data are UTC.
Comment 5•12 years ago
|
||
Bumping to worksforme per comment 4 - thanks Saptarshi
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Comment 6•12 years ago
|
||
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
Component: General → about:healthreport
Product: Webtools → Firefox Health Report
Updated•7 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•