Added changes to testcase.py for change server root
Added testvar to pass server_root from command line of telemetry-harness to testcase class.
Added argument.py and runner.py to implement MarionetteHarness in the test job
Changed test name in manifest.ini
MozReview-Commit-ID: 4XpBvq6Skz6
--HG--
extra : rebase_source : 15fafba89eecaa6347d29576ba55bf71296da31e
This pref is only set and maintained on Release and Beta (via the e10srollout
addon). Respecting it on Beta might cause us to read stale values.
MozReview-Commit-ID: ZDFdM41hw4
--HG--
extra : rebase_source : 2d9e7264b843cc90108c96824f06dc7a228dca28
Bug 1363672 uses .getStep() to obtain the step size for an input element in ms,
so we won't need to do conversion anymore. Bug 1364026 uses .getMinimum() and
.getMaximum() to obtain min and max in ms, rather than strings.
MozReview-Commit-ID: pFNcsqEaC0
--HG--
extra : rebase_source : dcba3a0c537580e0675db4cbe17a8d3209395014
Avoid the confusing state of "Stylo: true (disabled by build)" by also checking
the build constant _and_ the pref / env var together.
MozReview-Commit-ID: jTK66cWcyv
--HG--
extra : rebase_source : 54e158ed4f3dbde27e410aa0a59fcac44c383db3
Some tests were using "secret" APIs to get at telemetry knowledge from various
processes in various ways. Adjust them so that they work with the new ways of
doing things.
MozReview-Commit-ID: 2iBL00HVGyg
Previously we assumed count histograms were always present in payloads.
This was an erroneous assumption as count histograms were only 0 if they were
session histograms, or if they were from subsession histograms from subsessions
_after_ a subsession when they held a non-0 value.
So let's just treat count histograms as normal histograms from now on, without
any of this "sometimes 0" nonsense. This simplifies the code, tests, and our
understanding... and _should_ have few/zero downstream effects since the
existing behaviour was so poorly-understood (though exactly tested).
MozReview-Commit-ID: BH108ksygGw
TelemetrySession's getKeyedHistograms asks for each keyed histogram
individually. This is inefficient and doesn't work well with the storage
refactor.
So, plumb through a subsession keyed histogram snapshot API and convert
TelemetrySession over to using it.
MozReview-Commit-ID: Af9dTqw99UA
Previously we were doing bad string manipulation nonsense. Now when asked for
snapshots C++ can return a properly-formated Object tree.
MozReview-Commit-ID: HAvIbgzUvMU
Previously we used the base::StatisticsRecorder object for storage by name.
This is keyed by histogram name, which doesn't match our storage reality anymore.
Instead we use a name to refer to a set of histogram instances that record data from different processes, as well as separating session and subsession data.
In this re-write, we instead introduce the following lookup paths (managed in TelemetryHistogram.cpp):
- Main storage:
- (histogramId, processId, sessionOrSubsession) -> Histogram*
- (histogramId, processId) -> KeyedHistogram* (this handles subsessions internally)
- Lookup:
- (histogramName) -> histogramId
- (HistogramID) -> bool (is recording enabled for this histogram?)
This is wrapped with a few lookup functions.
This also allows us to keep HistogramIDs in the JS histogram instances now, instead of pointers to Histogram instances.
That means Histogram instance life-time management is now properly contained inside TelemetryHistogram.cpp.
MozReview-Commit-ID: 5yijGv7mc89
The Chromium IPC histogram code used the StatisticsRecorder object for storage.
This is keyed by histogram name, which doesn't match our storage reality anymore.
Instead we use a name to refer to a set of histogram instances that record data from different processes, as well as separating session and subsession data.
Consequently we need to rewrite this storage, which means StatisticsRecorder is not used anymore.
MozReview-Commit-ID: 1LC7YubpKaD
When we turn on the pref security.data_uri.unique_opaque_origin, this
test failed because data: URI is treated as cross origin. So I replace
the data: URI as a seperate xul.
The DownloadList object now provides batch notifications directly, in preparation for linking front-end views to other types of download lists without having to use the DownloadsData indirection.
MozReview-Commit-ID: FOTz1YwGRE1
--HG--
extra : rebase_source : df2d50d50c45a98e257caaa6efa9d0da2fa79237
extra : source : 278858e3d78b5e371f865adac043d07b770f1d3f
