CQ is not picking CL |
||||
Issue descriptionPlease explain below why you believe CQ is not working. I've checked Commit checkbox on https://codereview.chromium.org/1935923002/ but CQ is not reacting. This issue was created with help of the "CQ not working?" link on Rietveld.
,
May 1 2016
Yep, first time alert triggred at https://alertmanager.corp.google.com/#view=conditionDetails&query=[alertname=CQTaskDown,job=monarch-bridge,monitorname=monarch,service=chrome-infra,shard=0,zone=monarch] 02 PDT May 1st. This is right after this https://chrome-internal.googlesource.com/infra/infra_internal/+/0ce83caeca5aa0cf39409e11d3067d93e84e6d36 was landed and deployed to CQ.
,
May 1 2016
Revert: https://chromereviews.googleplex.com/418977013/ Deploying CQ now manually.
,
May 1 2016
Verified that CQ is working on your patch, Nodir. Thanks for report!
,
May 2 2016
Issue 608216 has been merged into this issue.
,
May 2 2016
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra.git/+/1395de0ac90e8a6d53031d4eda3f58e9dbc2c492 commit 1395de0ac90e8a6d53031d4eda3f58e9dbc2c492 Author: sergiyb <sergiyb@chromium.org> Date: Mon May 02 18:06:18 2016 Use correct types for the command line arguments R=tandrii@chromium.org BUG= 608217 Review-Url: https://codereview.chromium.org/1939863002 [modify] https://crrev.com/1395de0ac90e8a6d53031d4eda3f58e9dbc2c492/infra_libs/event_mon/config.py
,
May 3 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by tandrii@google.com
, May 1 2016Owner: tandrii@chromium.org
Status: Started (was: Untriaged)