Issue metadata
Sign in to add a comment
|
Failure to apply changes for no good reason |
||||||||||||||||||||
Issue descriptionThis happens a lot lately. Perfectly normal sequence of patches. Why does it try to add CL:450739 to the commit queue without even trying the CLs it depends on (which are all marked commit-ready) ? No idea if it is a UI issue or some other problem. This started happening a couple of weeks ago. Message added to CL: The Commit Queue failed to apply your change in https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/13900 . CL:450739 depends on CL:452757, which was not eligible (wrong manifest branch, wrong labels, or otherwise filtered from eligible set). Commit queue documentation: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium-os/commit-queue-overview
,
Mar 9 2017
,
Apr 6 2017
The ChromeOS commit queue is not maintained by the chrome infra team, and is not being changed in the chromium migration from rietveld to gerrit. Moving into the appropriate component.
,
May 16 2017
Sorry, looks like we missed this with the component change. Please re-open if you have a more recent example you'd like us to look into! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by logan@google.com
, Mar 9 2017Labels: Proj-Gerrit-Migration