Issue metadata
Sign in to add a comment
|
Document what "Tree Closers" mean for go/perfbot-sheriff |
||||||||||||||||||||||||
Issue descriptionSee https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/main.md Many of the bugs on https://sheriff-o-matic.appspot.com/chromium.perf are "Tree Closers", but it's unclear what that means and it isn't documented.
,
Nov 27
Found this as well: https://cs.chromium.org/chromium/infra/go/src/infra/monitoring/messages/alerts.go?type=cs&q=infra/monitoring/messages+Severity&g=0&l=91 "TreeCloser is an alert which closes the tree. Highest priority alert." I'm wondering how perf tree can even be closed.?
,
Nov 28
Gatekeeper sets the "tree status" on other projects' *-status.appspot.com apps, e.g. http://chromium-status.appspot.com/ and their CQ will not merge any CLs while that app says their tree is closed. chromium.perf does have an entry in the gatekeeper config: https://cs.chromium.org/chromium/build/scripts/slave/gatekeeper.json?g=0&l=615 But I'm don't see a chromeperf-status.appspot.com app though (and I'm also not sure SoM is interpreting that config the same way gatekeeper would). So these may just be regular alerts for chrome.perf sheriff's purposes.
,
Dec 18
,
Dec 18
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by crouleau@google.com
, Nov 27