Issue metadata
Sign in to add a comment
|
Buildbucket plugin did not reuse builds from patchset with real change |
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: Originally reported via email to Skia Infra: I made a CL (https://skia-review.googlesource.com/c/6467). I accidentally gave it a CR +1 and CQ +2, which I didn't want to do. I cancelled the CQ, so I could instead observe the results of a Dry Run. However, at this point I can't actually get it to trigger a full dry run. Even after removing my own CR +1, and editing the description to force creation of a new PS, every time I +1 CQ, it just runs Skia Presubmit, but none of the other standard bots. What is the expected behavior? What went wrong? See above. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Dec 27 2016
,
Dec 27 2016
Looks like a bug in the buildbucket plugin. Since the difference between patchset 1 and patchset 3 is just a description change, patchset 3 should have inherited the builds from the previous patchset. Looks like the presubmit run in patchset 2 and patchset3 confused the plugin.
,
Dec 28 2016
,
Jan 4 2017
Yes, it is re-using the builds for the prior patchset (because the code didn't change from the prior patchset) but the plugin doesn't yet display results from prior patchsets. That code has been written, and is just awaiting a deployment from the Gerrit folks.
,
Jan 5 2017
I now see all the tryjobs from PS1 displayed on PS2 and the subsequent patchsets. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by brianosman@chromium.org
, Dec 27 2016