Since we don't atomically retrieve session and subsession snapshots, there's
a possibility that off-thread accumulations can happen in between the two
getPayload calls in test_checkSubsessionHistograms.
CYCLE_COLLECTOR_WORKER* are the obvious first choice.
MozReview-Commit-ID: 5lseRAJ1Rg6
--HG--
extra : rebase_source : 219ed38e526483627792ed4c177f49c1537c3f07
This patch enables sending the "update" ping with reason "success"
after the browser is restarted when an update is successfully applied.
MozReview-Commit-ID: 8LYxhTTrs7l
--HG--
extra : rebase_source : 1f66417adbc6b0126c2e7436c994a0b93a3f4cdc
With the removal of the old addonHistograms, all histograms are now registered.
So removing registered(Keyed)Histograms should be straightforward?
Unfortunately not, as this was how we filtered data based on dataset
(opt-in/opt-out), so a little more fiddling was needed to get C++ to only
serialize dataset-appropriate data (instead of post-facto filtering it in JS).
MozReview-Commit-ID: HDplhmzmzJl
--HG--
extra : rebase_source : 9c38c97e39e3c4fb192288d751505e1f0f2a2c6d
On very fast builds (OPT, PGO) this test can fail intermittently because the time it takes to send a ping and receive a reply is 0. Account for that by replacing all the "greater than" checks with "greater or equal than".
MozReview-Commit-ID: JvEo2rCbJj6
--HG--
extra : rebase_source : 17ea1ccf2e0a69c98eaaa64ef94db29983b21591
Sometimes, test receive pings that should not be there. This happens because
Telemetry is initialized multiple times by some tests: this patch fixes
one test and moves another flaky test to a separate file. Additionally,
add useful debug information to the logs to understand which ping made
the test fail.
MozReview-Commit-ID: BS25U3e9fxO
--HG--
extra : rebase_source : 697142688c9562c4c64c7a81908d9360fc4d04f4
A new test using the new APIs is introduced in a later part. This test no longer
functions as ThreadHangStats is no longer present.
MozReview-Commit-ID: HKmoP2An4GP
A new test using the new APIs is introduced in a later part. This test no longer
functions as ThreadHangStats is no longer present.
MozReview-Commit-ID: HKmoP2An4GP
To cut down on complexity, we don't require specifying any expiry versions.
Given that these events will be recorded non-persistently from off-train add-ons, they can be expired by shipping new add-on releases.
We also start to use the new "record on release" terminology here instead of opt-in/opt-out, but are not changing the internal functionality yet.
Technically, this is implemented by keeping a separate registry for the dynamic event information.
Built-in & dynamic events are tracked with separate numeric ids, so introduce a common identifier for both, an EventKey.
For actual event storage, the events are treated the same as built-in events. They are simply bucketed into the 'dynamic' process storage.
This approach ends up duplicating code paths that use the event info, but keeps a single implementation for recording, storage & serialization.
--HG--
extra : rebase_source : 639f9353a7e9383efe87f7f059ca83b56fb3b2a7
Added callback to testcase.py. Made sure callback is callable.
Added callback in test_main_tab_scalars to be the browser restart.
Added callback in test_ping_server_received_ping to None because no callback is needed.
MozReview-Commit-ID: Jf4YHasCXVg
--HG--
extra : rebase_source : f2b54f151d40436598003c009cc8a9b06bb052af
Adam Gashlin
Sebastian Hengst
Georg Fritzsche
Chris H-C
Ryan VanderMeulen
Anthony Miyaguchi
Julian Descottes
Alessio Placitelli
Wes Kocher
David Major
Kate Ustiuzhanina
Michael Layzell
Rajesh Kathiriya
Phil Ringnalda
Marco Castelluccio
Luciano Italiani
John Dorlus
Carsten "Tomcat" Book
Andrew Halberstadt
Alejandro Rodriguez Salamanca