Issue metadata
Sign in to add a comment
|
Bugdroid fails to update bugs when comma-separated IDs are specified in BUG= field. |
||||||||||||||||||||||||
Issue descriptionWhen I landed https://chromium-review.googlesource.com/c/411864/ containing the following bug field: BUG=657572, 665874 , only the first bug got a bugdroid post: https://bugs.chromium.org/p/chromium/issues/detail?id=657572 The second bug https://bugs.chromium.org/p/chromium/issues/detail?id=665874 didn't get a post. A similar bug seems to exist for the Gerrit UI (I didn't look for it a bug exists for that). AFAIK, the comma-separated way of specifying bugs have always been supported in the past.
,
Nov 22 2016
The bugdroid for chromium/tools/build hasn't changed due to Gerrit. It still just polls the git repository directly, exactly as it did when we were using Rietveld for that repo. This appears to just be a coincidence: yes, the gerrit UI doesn't autolink the second bug in a single line (see bug for that here ), but this seems to have just been a normal failure of bugdroid being bugdroid. Here's the log of that run: https://luci-logdog.appspot.com/v/?s=infra-internal%2Fbb%2Finternal.infra.cron%2Fbugdroid%2F27017%2F%2B%2Frecipes%2Fsteps%2Fbugdroid%2F0%2Fstdout# You can see that it correctly parses both bugs in the line. You can also see that there's nothing in the logic that should prevent it from posting to both: https://cs.chromium.org/chromium/infra/infra/services/bugdroid/bugdroid.py?q=%22for+bug+in+bugs:%22&sq=package:chromium&l=128&dr=C The log simply doesn't print the second "Attempting to save" statement. I have no idea what went wrong. But I'm going to dupe this into a generic "bugdroid sometimes sucks" bug, rather than believe that this is related to gerrit. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by andyb...@chromium.org
, Nov 21 2016Owner: aga...@chromium.org
Status: Assigned (was: Untriaged)