QA/Telemetry/State&ErrorCodes: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
The following document has a link to the code that defines the state and error codes that you might encounter in the browser console while testing a telemetry experiment. | The following document has a link to the code that defines the state and error codes that you might encounter in the browser console while testing a telemetry experiment. | ||
A quick example of a log that has both a state and an error code that isn't defined: | |||
ExperimentEntry #0::_installAddon() - AddonInstall onDownloadFailed for tile-switcher@experiments.mozilla.org, | ExperimentEntry #0::_installAddon() - AddonInstall onDownloadFailed for tile-switcher@experiments.mozilla.org, | ||
state=4, error=-2 | state=4, error=-2 | ||
In the above case, you would look up '''error=-2''' and '''state=4''' using the link below to see what each of the codes mean. | |||
* [https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/AddonManager.jsm#2930 Definitions of State & Error codes] | * [https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/AddonManager.jsm#2930 Definitions of State & Error codes] | ||
Revision as of 16:49, 15 January 2016
Quick Summary
The following document has a link to the code that defines the state and error codes that you might encounter in the browser console while testing a telemetry experiment.
A quick example of a log that has both a state and an error code that isn't defined:
ExperimentEntry #0::_installAddon() - AddonInstall onDownloadFailed for tile-switcher@experiments.mozilla.org, state=4, error=-2
In the above case, you would look up error=-2 and state=4 using the link below to see what each of the codes mean.