"cros tryjob --yet betty-vmtest-informational" fails oddly. |
||
Issue descriptionI thought this was already filed, but I can't find it. "cros tryjob --yet betty-vmtest-informational" fails because the value "builder_name" is null in the buildbucket request. Example buildbucket result: https://apis-explorer.appspot.com/apis-explorer/?base=https://cr-buildbucket.appspot.com/_ah/api#p/buildbucket/v1/buildbucket.get?id=8970326287936457152&_h=1&
,
Aug 25 2017
It used to be worked before Aug 22. Did the waterfall restart during that day? In addition to this, is it possible to add the builder to waterfall(is it implies that the builder will build itself automatically everyday?) so that we will not get the same issue in the future?
,
Aug 25 2017
I found that a CL I landed recently had a bug that's helping to cause this. I have a fix up now. https://chromium-review.googlesource.com/c/chromiumos/chromite/+/636046
,
Aug 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/b049418f25b1d37f6adfb9232bb0c656976e8a5e commit b049418f25b1d37f6adfb9232bb0c656976e8a5e Author: Don Garrett <dgarrett@google.com> Date: Sat Aug 26 02:54:14 2017 remote_try: Use default builder name if template is None. My CL:624672 attempted to make "_GetBuilder" more resilient, but incorrectly handled builders which don't use a template at all. BUG= chromium:759158 TEST=run_tests Change-Id: Ic69770dcf80a59fd2c496f612da4e7a4a985749f Reviewed-on: https://chromium-review.googlesource.com/636046 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Ningning Xia <nxia@chromium.org> [modify] https://crrev.com/b049418f25b1d37f6adfb9232bb0c656976e8a5e/cbuildbot/remote_try.py
,
Sep 5 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by dgarr...@chromium.org
, Aug 25 2017