Closed Bug 1186871 Opened 9 years ago Closed 9 years ago

Don't wait for "shutdown" ping saving before creating "saved-session" payloads

Categories

(Toolkit :: Telemetry, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla42
Tracking Status
firefox40 --- wontfix
firefox41 + fixed
firefox42 --- fixed

People

(Reporter: gfritzsche, Assigned: Dexter)

References

Details

(Whiteboard: [rC] [unifiedTelemetry] [uplift3])

Attachments

(2 files, 1 obsolete file)

After creating the "shutdown" ping, we wait for (potentially long) saving operations to finish before collecting the "saved-session" payload.
 
https://hg.mozilla.org/mozilla-central/annotate/2ddec2dedced/toolkit/components/telemetry/TelemetrySession.jsm#l1617

We should not wait on this before collecting the saved-session payload, instead kicking off both collections synchronously and afterwards waiting on both to be saved.
Assignee: nobody → alessio.placitelli
Attached patch bug1186871.patch (obsolete) (deleted) — Splinter Review
Attachment #8637911 - Flags: review?(gfritzsche)
Comment on attachment 8637911 [details] [diff] [review]
bug1186871.patch

Review of attachment 8637911 [details] [diff] [review]:
-----------------------------------------------------------------

r=me with the below fixed.

::: toolkit/components/telemetry/TelemetrySession.jsm
@@ +1613,5 @@
>  
>     /**
>      * Save both the "saved-session" and the "shutdown" pings to disk.
>      */
>    saveShutdownPings: Task.async(function*() {

This doesn't need to be a Task now.
Just make it a plain function and |return Promise.all(...)|.
Attachment #8637911 - Flags: review?(gfritzsche) → review+
Attached patch bug1186871.patch (deleted) — Splinter Review
Thanks! Try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f157d696aa5f
Attachment #8637911 - Attachment is obsolete: true
Attachment #8637953 - Flags: review+
https://hg.mozilla.org/mozilla-central/rev/a286f65dd231
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
Comment on attachment 8637953 [details] [diff] [review]
bug1186871.patch

Approval Request Comment
[Feature/regressing bug #]:
This is part of the uplift3 batch for the unified Telemetry project: http://bit.ly/1TCl4r8
This is targetting 41 now and these are the last minor "feature" patches blocking shipping - any further patches will be fixes for data quality etc. with very limited scope & impact.
[User impact if declined]:
This affects data quality, potentially increasing data mismatch between "old" and "new" Telemetry data, which could potentially break data validation.
[Describe test coverage new/current, TreeHerder]:
This has good automated test-coverage.
[Risks and why]:
Low-risk, well understood change that just changes when ping data is generated.
[String/UUID change made/needed]:
No string changes.
Attachment #8637953 - Flags: approval-mozilla-aurora?
Tracked for 41. Also requesting QE team to verify this fix along all Unified Telemetry fixes. Thanks!
Flags: qe-verify+
Comment on attachment 8637953 [details] [diff] [review]
bug1186871.patch

Let's uplift to Aurora, has been in m-c for a few days now.
Attachment #8637953 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Attached patch bug1186871.patch (AURORA) (deleted) — Splinter Review
This updated patch fixes the problem for aurora.
Flags: needinfo?(alessio.placitelli)
Attachment #8640999 - Flags: review+
Attachment #8640999 - Flags: feedback?(gfritzsche)
Attachment #8640999 - Flags: feedback?(gfritzsche) → feedback+
I don't think this bug needs separate QA attention.
Flags: qe-verify+ → qe-verify-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: