Telemetry for Shumway

RESOLVED FIXED in Firefox 27

Status

Firefox Graveyard
Shumway
P1
normal
RESOLVED FIXED
4 years ago
a year ago

People

(Reporter: elan, Assigned: yury)

Tracking

unspecified
Firefox 27

Details

(Whiteboard: [shumway] fixed-upstream, https://github.com/mozilla/shumway/pull/821)

Attachments

(1 attachment, 3 obsolete attachments)

(Reporter)

Description

4 years ago
We would like to use Telemetry in order to measure and track a spectrum of performance and usage metrics for Shumway. Placing in Firefox 'general' component for now.

Comment 1

4 years ago
Hello, I'd like to work on this project. Could you give me some details about how should I do? And where I can find Shumway?
Georgiana you can join us in the #shumway IRC room, we can answer all your questions there.
(Reporter)

Updated

4 years ago
Component: General → Shumway
(Assignee)

Updated

4 years ago
Blocks: 904346
(Reporter)

Updated

4 years ago
Priority: -- → P1
(Assignee)

Comment 3

4 years ago
Created attachment 813338 [details] [diff] [review]
Histograms for Shumway
(Assignee)

Comment 4

4 years ago
Enumeration assignments are defined at https://github.com/mozilla/shumway/wiki/Enumeration-Assignments-for-the-Telemetry-Histograms
(Assignee)

Comment 5

4 years ago
Created attachment 817959 [details] [diff] [review]
bug900566-histograms.diff

(will be required for https://github.com/mozilla/shumway/pull/821)
Attachment #813338 - Attachment is obsolete: true
(Assignee)

Comment 6

4 years ago
Created attachment 818049 [details] [diff] [review]
bug900566-histograms.diff
Attachment #817959 - Attachment is obsolete: true
(Assignee)

Comment 7

4 years ago
Created attachment 818548 [details] [diff] [review]
bug900566-histograms.diff

Selecting reviewer based on bug 894546
Attachment #818049 - Attachment is obsolete: true
Attachment #818548 - Flags: review?(nfroyd)
Attachment #818548 - Flags: review?(nfroyd) → review+
(Assignee)

Updated

4 years ago
Assignee: nobody → ydelendik
Keywords: checkin-needed
Whiteboard: keep-open, fixed-upstream, https://github.com/mozilla/shumway/pull/821
remote:   https://hg.mozilla.org/integration/mozilla-inbound/rev/fd5fe2e742f6
Status: NEW → ASSIGNED
Keywords: checkin-needed
https://hg.mozilla.org/integration/fx-team/rev/d93b0dd959b3
Whiteboard: keep-open, fixed-upstream, https://github.com/mozilla/shumway/pull/821 → [leave open]fixed-upstream, https://github.com/mozilla/shumway/pull/821[fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/d93b0dd959b3
Whiteboard: [leave open]fixed-upstream, https://github.com/mozilla/shumway/pull/821[fixed-in-fx-team] → [leave open]fixed-upstream, https://github.com/mozilla/shumway/pull/821
https://hg.mozilla.org/mozilla-central/rev/fd5fe2e742f6
Sorry, but I had to back this out because we suspect that one of the 4 patches in this push has caused frequent failures in the mochitest-bc suite (see <https://tbpl.mozilla.org/?tree=Fx-Team&fromchange=8904c520ed40&tochange=39500fdd5007&jobname=browser-chrome>).  Please verify that your patch is not the culprit by running it through the try server and verifying that multiple retriggers of the mochitest-bc suite are all green, and then request checkin-needed again.

Thanks!

(Backout: https://hg.mozilla.org/mozilla-central/rev/385fc5d956db)
Relanded in https://hg.mozilla.org/integration/fx-team/rev/520f2bffeaea once we finally found something better to blame.
https://hg.mozilla.org/mozilla-central/rev/520f2bffeaea
(Reporter)

Updated

4 years ago
Whiteboard: [leave open]fixed-upstream, https://github.com/mozilla/shumway/pull/821 → [leave open]fixed-upstream, https://github.com/mozilla/shumway/pull/821, [shumway]
(Assignee)

Comment 15

4 years ago
Logic landed with bug 928969
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Whiteboard: [leave open]fixed-upstream, https://github.com/mozilla/shumway/pull/821, [shumway] → [shumway] fixed-upstream, https://github.com/mozilla/shumway/pull/821
Target Milestone: --- → Firefox 27
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.