97
edits
TestEngineering/Performance/Raptor: Difference between revisions
Jump to navigation
Jump to search
Add information on disabling test alerts.
(Change contact and update browsers we test on.) |
(Add information on disabling test alerts.) |
||
| Line 82: | Line 82: | ||
And push that change to Try (./mach try fuzzy --full) and run the Raptor page-load test. | And push that change to Try (./mach try fuzzy --full) and run the Raptor page-load test. | ||
==== Disabling Alerts ==== | |||
It is possible to disable alerting for all our performance tests. Open the target test manifest such as the raptor-tp6*.ini file ([https://searchfox.org/mozilla-central/source/testing/raptor/raptor/tests Raptor tests folder]), and make sure there are no <tt>alert_on</tt> specifications. | |||
When it's removed there will no longer be a <tt>shouldAlert</tt> field in the output perferhder data (you can find the [https://searchfox.org/mozilla-central/source/testing/mozharness/external_tools/performance-artifact-schema.json#68,165 schema here]). As long as <tt>shouldAlert</tt> is not in the data, no alerts will be generated. If you need to also disable code sheriffing for the test, then you need to change the tier of the task to 3. | |||
=== Benchmark Tests === | === Benchmark Tests === | ||