Enable alerting benchmark_duration metrics of ref build benchmarks |
|||
Issue descriptionRef build benchmarks share the same machines with TOT benchmarks, so it's equally important for us to make sure that their cycle time don't blow up. Assign to Simon for triaging.
,
Apr 24 2017
We might need to add a special case in _FilterAnomaliesFoundInRef here: https://github.com/catapult-project/catapult/blob/master/dashboard/dashboard/find_anomalies.py#L152 I think benchmark_duration is the only metric we'd want alerts on the ref build for.
,
Apr 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/92cdfb91a7cf3336717c3375aa7acf0a9b976110 commit 92cdfb91a7cf3336717c3375aa7acf0a9b976110 Author: catapult-deps-roller@chromium.org <catapult-deps-roller@chromium.org> Date: Mon Apr 24 21:04:15 2017 Roll src/third_party/catapult/ b8345e64e..5671bb03d (1 commit) https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/b8345e64e254..5671bb03d416 $ git log b8345e64e..5671bb03d --date=short --no-merges --format='%ad %ae %s' 2017-04-24 simonhatch Dashboard - Alert on ref for benchmark_duration. Created with: roll-dep src/third_party/catapult BUG= 714616 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=sullivan@chromium.org Change-Id: I12b4ca6b5abd67f3324e0567d68d1b319ba3728a Reviewed-on: https://chromium-review.googlesource.com/486141 Reviewed-by: <catapult-deps-roller@chromium.org> Commit-Queue: <catapult-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#466761} [modify] https://crrev.com/92cdfb91a7cf3336717c3375aa7acf0a9b976110/DEPS
,
Jul 18 2017
,
Aug 10 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by nedngu...@google.com
, Apr 24 2017