Michael or Aaron, can one of you help triage/own this?

Passing to Aaron for re-triage since Sheng left.

Friendly ping. bugdroid is a little spammy right now on BoringSSL changes. I imagine it's just a config change?

Sorry, I thought this was fixed with the inclusion of "refs/heads/master" as a filter on the boringssl bugdroid config ages ago, but it turns out that's a regex, and refs/heads/master-with-bazel matches the regex too :)

I've filed a pair of CLs to resolve this. A bigger refactoring of bugdroid's ref-matching code would be nice, but I just spent an hour going down that rabbit hole and didn't get anywhere good so I'm doing this the dumb way.
https://chromereviews.googleplex.com/515697013
https://chromium-review.googlesource.com/387669

Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra.git/+/a0f3bb5a315f594286754d178e4c52594debc3b1

commit a0f3bb5a315f594286754d178e4c52594debc3b1
Author: Aaron Gable <agable@chromium.org>
Date: Wed Sep 21 21:46:16 2016

Make bugdroid match full refs, not ref prefixes

BUG= 626421 

Change-Id: I46f99267a2b934a8f43f861a09d8fd8ca9350673
Reviewed-on: https://chromium-review.googlesource.com/387669
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Commit-Queue: Aaron Gable <agable@chromium.org>

[modify] https://crrev.com/a0f3bb5a315f594286754d178e4c52594debc3b1/infra/services/bugdroid/gob_helper.py

Those two CLs have been landed and deployed. This should now be fixed. Can you verify?

Seems to be good now. Thanks!