Confirmed users
513
edits
EngineeringProductivity/Projects/ActiveData: Difference between revisions
EngineeringProductivity/Projects/ActiveData (view source)
Revision as of 15:49, 29 July 2015
, 29 July 2015Add list of stuff NOT indexed
Klahnakoski (talk | contribs) (it has been 3 months, total rewrite) |
Klahnakoski (talk | contribs) (Add list of stuff NOT indexed) |
||
| Line 21: | Line 21: | ||
== Limitations == | == Limitations == | ||
The unittest data is limited to those test suites that generate structured logs. Currently (July 29, 2015) the following do NOT have structured logs, and are NOT in ActiveData: | |||
* reftest | |||
* jsreftest | |||
* crashtest | |||
* cppunittest | |||
* talos | |||
* and any of the js based gaia suites (e.g Gij) | |||
* buildbot | |||
* mozharness | |||
Specifically, you can see if a structured log is being generated: In treeherder, click a job. Under the "Job details" pane at the bottom, look for a line similar to: | |||
<blockquote> ''artifact uploaded: <suite>_raw.log'' | |||
</blockquote> | |||
If you see that, it is using structured logging. | |||
ActiveData makes specific tradeoffs to achieve its goals. It has the following limitations: | ActiveData makes specific tradeoffs to achieve its goals. It has the following limitations: | ||
* large memory requirements | * large memory requirements | ||