https://chromium-review.googlesource.com/#/c/344601/ still not picked up by the CQ. Do you see a "Submit" button in that CL? That should be independent from the CQ issue.

The pre-cq launcher needs to be reset to pick up the new chromite code. I'll do that now.

Looks like we may be having an issue with this. https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/11164/steps/CommitQueueCompletion/logs/stdio

06:38:53: WARNING: git push failed for /b/cbuild/internal_master/src/aosp/system/connectivity/shill:master; was a change chumped in the middle of the CQ run?
Traceback (most recent call last):
  File "/b/cbuild/internal_master/chromite/cbuildbot/validation_pool.py", line 2076, in PushRepoBranch
    git.GitPush(repo, 'HEAD', push_to, skip=self.dryrun)
  File "/b/cbuild/internal_master/chromite/lib/git.py", line 1250, in GitPush
    RunGit(git_repo, cmd, retry=retry, capture_output=capture_output)
  File "/b/cbuild/internal_master/chromite/lib/git.py", line 829, in RunGit
    ['git'] + cmd, **kwargs)
  File "/b/cbuild/internal_master/chromite/lib/retry_util.py", line 88, in GenericRetry
    ret = functor(*args, **kwargs)
  File "/b/cbuild/internal_master/chromite/lib/cros_build_lib.py", line 619, in RunCommand
    raise RunCommandError(msg, cmd_result)
RunCommandError: return code: 1; command: git push https://chromium-review.googlesource.com/aosp/platform/system/connectivity/shill HEAD:master
remote: 
remote: Processing changes: refs: 1        
remote: Processing changes: refs: 1, done            
To https://chromium-review.googlesource.com/aosp/platform/system/connectivity/shill
 ! [remote rejected] HEAD -> master (prohibited by Gerrit)
error: failed to push some refs to 'https://chromium-review.googlesource.com/aosp/platform/system/connectivity/shill'

Trying to normalize aosp ACLs with the rest of chromiumos repos. https://chromium-review.googlesource.com/#/c/344742/

looks like fixed now; need to double check that the last CL didn't break the mirroring.

Do we have a bug open about the IsBranchable behavior? Still want to fix that before the next branch cut.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/5cd848ff671b97d5c0e73062219026fde5b56e34

commit 5cd848ff671b97d5c0e73062219026fde5b56e34
Author: Aviv Keshet <akeshet@chromium.org>
Date: Tue May 31 19:41:40 2016

chromeos_config: make aosp/ projects branchable

BUG= chromium:612231 
TEST=manual test of re

Change-Id: Ia61d26cb6b7b92c095926e32120e51f1c43380a8
Reviewed-on: https://chromium-review.googlesource.com/348382
Commit-Ready: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/5cd848ff671b97d5c0e73062219026fde5b56e34/cbuildbot/config_lib.py
[modify] https://crrev.com/5cd848ff671b97d5c0e73062219026fde5b56e34/cbuildbot/chromeos_config.py

There's an owner on this bug but the status != Assigned. Fixing. If you feel you don't own this bug, please remove yourself as the owner and mark it as "Available" or "Untriaged".