New issue
Advanced search Search tips

Issue 706896 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 705023



Sign in to add a comment

CLs got rejected by Pre-CQs because dependent CLs weren't screened

Project Member Reported by nxia@chromium.org, Mar 30 2017

Issue description

CLs got rejected by Pre-CQs because their dependent CLs weren't screened in the same run. 


Follow up the CL:*333889
https://luci-milo.appspot.com/buildbot/chromeos/pre-cq-launcher/8825


https://chrome-internal-review.googlesource.com/c/333889

CL:*333889 was set as reset_pre_cq in the previous run.
http://shortn/_zfh4DPCwsD

In the next run, progress_map was generated before the CL:*333889 was screened again. 
http://shortn/_NxZaFGGWnA

Then CL:*333889 was screened and corresponding CLActions were inserted
http://shortn/_Lb1oxPZA1P

CL:*333889 wasn't in the progress_map, and so PatchNotEligible was thrown and the CL set were rejected.

Please find more context in  crbug.com/705023  comment #6
 
Blocking: 705023
Status: Assigned (was: Untriaged)
This bug is Untriaged and very old.  Because it has an owner, the status will be set to assigned to avoid closing a bug someone is using.  If this bug still needs triage, change it back to Untriaged.

Comment 3 by nxia@chromium.org, May 18 2018

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment