Closed
Bug 1119281
Opened 9 years ago
Closed 9 years ago
ClientID is missing
Categories
(Toolkit :: Telemetry, defect)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
mozilla38
Tracking | Status | |
---|---|---|
firefox35 | --- | unaffected |
firefox36 | --- | fixed |
firefox37 | --- | fixed |
firefox38 | --- | fixed |
People
(Reporter: rvitillo, Assigned: gfritzsche)
References
Details
Attachments
(1 file, 1 obsolete file)
5.71 KB,
patch
|
gfritzsche
:
review+
Sylvestre
:
approval-mozilla-aurora+
Sylvestre
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
It seems that all clientIDs went missing after Bug 1101487 landed, see http://nbviewer.ipython.org/gist/vitillo/942eb0931e4b626cca25
Comment 1•9 years ago
|
||
There are some clientIDs appearing in "idle-daily" submissions for builds in that time period, though they do appear to be missing in the raw incoming data for "saved-session" pings too.
Assignee | ||
Comment 2•9 years ago
|
||
mreid checked the raw data server-side: > <mreid> gfritzsche: looks like we're receiving some on "idle-daily" but not on "saved-session" > <gfritzsche> mreid: strange ok - starting in that timeframe too i assume? > <mreid> gfritzsche: there are only a small number of submissions from that time range in the raw data I'm looking at, so it's hard to say for sure > <mreid> but the last "present" one on saved-session so far is from 12/17 I wonder if we do happen to save/serialize pings after we hit TelemetryPing.uninstall() here: https://hg.mozilla.org/mozilla-central/annotate/70de2960aa87/toolkit/components/telemetry/TelemetryPing.jsm#l1166 ... as we null out the clientID there - which was a change from bug 1101487. The other changes don't seem like they shouldn't affect the clientID submissions negatively.
Assignee | ||
Comment 3•9 years ago
|
||
Bug 1101487 made TelemetryPing.uninstall() clear out the clientID. However, telemetry session save on shutdown happens after uinstall(), so we lost the client id there. This changes things to not affect this path and adds some test coverage. AsyncShutdown phase state etc. are hard to reset, so this goes for a specialized testing shutdown path.
Comment 4•9 years ago
|
||
Comment on attachment 8546790 [details] [diff] [review] Fix Review of attachment 8546790 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/telemetry/TelemetryPing.jsm @@ +1313,5 @@ > get clientID() { > return this._clientID; > }, > + > + shutdown: function(testing=false) { - Write documentation comment above function - spacing.. testing = false
Attachment #8546790 -
Flags: review?(vdjeric) → review+
Assignee | ||
Comment 5•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/7475b716558d
This apparently turned xpcshell tests on Windows permafail: https://treeherder.mozilla.org/logviewer.html#?job_id=5292616&repo=mozilla-inbound Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/9739ef7c3d2f
Assignee | ||
Comment 7•9 years ago
|
||
I don't see that failure locally, pushed to try to cross-check: https://treeherder.mozilla.org/#/jobs?repo=try&revision=2b4a2bd7ff39 https://tbpl.mozilla.org/?tree=Try&rev=2b4a2bd7ff39
Assignee | ||
Comment 8•9 years ago
|
||
I finally noticed a missing yield in the test: https://treeherder.mozilla.org/#/jobs?repo=try&revision=42e0b675961b https://tbpl.mozilla.org/?tree=Try&rev=42e0b675961b
Assignee | ||
Comment 10•9 years ago
|
||
Attachment #8546790 -
Attachment is obsolete: true
Assignee | ||
Updated•9 years ago
|
Attachment #8552642 -
Flags: review+
Comment 11•9 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/df2f2df820a8
Keywords: checkin-needed
Whiteboard: [fixed-in-fx-team]
Comment 14•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/df2f2df820a8
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla38
Assignee | ||
Comment 15•9 years ago
|
||
Mark, can you confirm this fix server-side?
status-firefox35:
--- → unaffected
status-firefox36:
--- → affected
status-firefox37:
--- → affected
status-firefox38:
--- → fixed
Flags: needinfo?(mreid)
Comment 16•9 years ago
|
||
I checked a small sample of incoming pings, and I'm seeing clientIDs in saved-session pings from nightly buildids after 20150123. Please let me know if further checking is required.
Flags: needinfo?(mreid)
Assignee | ||
Comment 17•9 years ago
|
||
Comment on attachment 8552642 [details] [diff] [review] Fix Approval Request Comment [Feature/regressing bug #]: Follow-up for bug 1101487. [User impact if declined]: Missing client id in telemetry saved-session pings [Describe test coverage new/current, TreeHerder]: improved automated test-coverage, confirmed server-side. [Risks and why]: Rather low risk of some side-effects on telemetry, but this should have shown up by now. [String/UUID change made/needed]: None.
Attachment #8552642 -
Flags: approval-mozilla-beta?
Attachment #8552642 -
Flags: approval-mozilla-aurora?
Updated•9 years ago
|
Attachment #8552642 -
Flags: approval-mozilla-beta?
Attachment #8552642 -
Flags: approval-mozilla-beta+
Attachment #8552642 -
Flags: approval-mozilla-aurora?
Attachment #8552642 -
Flags: approval-mozilla-aurora+
Comment 18•9 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/4445d5ab227f Needs rebasing for beta uplift.
Assignee | ||
Comment 19•9 years ago
|
||
I'll wait for confirmation on bug 1128135 before doing a beta uplift.
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(gfritzsche)
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Comment 20•9 years ago
|
||
The dashboard recovered after bug 1128135: http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetrics60DaysAggregator/outputs/TelemetryChannelMetrics60DaysAggregator.nightly.cbuf I rolled bug 1128135 into the beta patch and landed that: https://hg.mozilla.org/releases/mozilla-beta/rev/ced08a06e2d1
Updated•9 years ago
|
Keywords: branch-patch-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•