Skip to content

A
angle
Commit 75de9ef2 by Jonah Ryan-Davis Committed by Commit Bot
Options

Add perf-alert monitoring instruction to docs

Bug: angleproject:1944 Change-Id: Idee9a3b749b7f618c221f85be54e1331259a8dce Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2446852 Commit-Queue: Jonah Ryan-Davis <jonahr@google.com> Reviewed-by: 's avatarShahbaz Youssefi <syoussefi@chromium.org> Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
parent 848ab12d
Showing with 7 additions and 0 deletions
infra/ANGLEWrangling.md
...@@ -11,6 +11,7 @@ As an ANGLE Sheriff. Your job is to: ...@@ -11,6 +11,7 @@ As an ANGLE Sheriff. Your job is to:
1. Keep the [ANGLE Standalone Testers](README.md) in good working order. 1. Keep the [ANGLE Standalone Testers](README.md) in good working order.
1. Keep the [SwANGLE Try Waterfall](https://luci-milo.appspot.com/p/chromium/g/tryserver.chromium.swangle/builders) in good 1. Keep the [SwANGLE Try Waterfall](https://luci-milo.appspot.com/p/chromium/g/tryserver.chromium.swangle/builders) in good
working order. working order.
1. Monitor and respond to ANGLE's [Perf alerts](https://groups.google.com/u/0/a/chromium.org/g/angle-perf-alerts)
If you're not an ANGLE team member, you can contact us on the public ANGLE project If you're not an ANGLE team member, you can contact us on the public ANGLE project
[Google group](https://groups.google.com/forum/#!forum/angleproject). [Google group](https://groups.google.com/forum/#!forum/angleproject).
...@@ -140,3 +141,9 @@ The possible ways to handle these failures are: ...@@ -140,3 +141,9 @@ The possible ways to handle these failures are:
A lower priority task here is to keep healthy all the SwANGLE A lower priority task here is to keep healthy all the SwANGLE
[CI](https://luci-milo.appspot.com/p/chromium/g/chromium.swangle/builders) and [CI](https://luci-milo.appspot.com/p/chromium/g/chromium.swangle/builders) and
[Try](https://luci-milo.appspot.com/p/chromium/g/tryserver.chromium.swangle/builders) bots. [Try](https://luci-milo.appspot.com/p/chromium/g/tryserver.chromium.swangle/builders) bots.
## Task 6: Monitor and respond to ANGLE's perf alerts
Any large regressions should be triaged with a new ANGLE bug linked to any suspected CLs that may
have caused performance to regress. If it's a known/expected regression, the bug can be closed as
such. The tests are very flaky right now, so a WontFix resolution is often appropriate.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment