cbuildbot: Unable to produce factory image on factory-rambi-6420.B |
||||
Issue descriptionRunning: cros tryjob -b factory-rambi-6420.B -g 689962 --remote enguarde-factory Fails very early in: https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/factory/builds/9 23:23:03: INFO: RunCommand: /b/c/cbuild/repository/chromite/bin/cbuildbot enguarde-factory --buildroot /b/c/cbuild/repository --branch master --buildnumber 9 --buildbucket-id 8967144801826413936 --remote-trybot -b factory-rambi-6420.B -g 689962 in /b/c/cbuild/repository Usage: cbuildbot [options] buildbot_config [buildbot_config ...] cbuildbot: error: no such option: --buildbucket-id buildbucket-id has been added in cl/361400 on 07/18/17. Does it need to be backported on older branch to be able to build them?
,
Sep 29 2017
Hum??? It's supposed to be auto-filtered out based on the option API version. Did that option not get one?
,
Dec 9 2017
,
Dec 12 2017
I checked. --buildbucket-id does NOT have an API version. I'm picking an old version and adding it as a rough workaround.
,
Dec 12 2017
,
Dec 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/b01a8e640ef81e1bb27d55c5241b92b273e1088f commit b01a8e640ef81e1bb27d55c5241b92b273e1088f Author: Don Garrett <dgarrett@google.com> Date: Wed Dec 13 02:40:04 2017 cbuildbot: Add api to --buildbucket-id. Old enough branches will fail because cbuildbot_launch will pass along the unknown option --buildbucket-id. This adds an API version to the option to prevent this. I'm using for a version (REEXEC_API_GOMA) added after buildbucket-id, but that means that some branches which could understand --buildbucket-id won't get it. BUG= chromium:770213 TEST=Manual cbuildbot_launch invocation with factory-rambi-6420.B Change-Id: I0bbdb0f87c5260b1d66f1f56b8cc2084511b5d21 Reviewed-on: https://chromium-review.googlesource.com/821611 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/b01a8e640ef81e1bb27d55c5241b92b273e1088f/scripts/cbuildbot.py
,
Dec 13 2017
In theory, this is fixed. Running a verification tryjob here: https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/factory/builds/25
,
Dec 13 2017
The tryjob failed because I tried to test a CL that has already been submitted. However, it got well past the previous problem.
,
Jul 30
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vapier@chromium.org
, Sep 29 2017Owner: dgarr...@chromium.org