main.py: error: no such option: --cache-dir
21:09:38: WARNING: Command failed with retriable error.
return code: 2; command: repo --time sync '--cache-dir=/b/cros_git_cache' -n
cwd=/b/cbuild/shared_internal
21:09:38: ERROR: return code: 2; command: repo --time sync '--cache-dir=/b/cros_git_cache' -n
cwd=/b/cbuild/shared_internal

@@@STEP_FAILURE@@@
21:09:38: ERROR: <class 'chromite.cbuildbot.repository.SrcCheckOutException'>: return code: 2; command: repo --time sync '--cache-dir=/b/cros_git_cache' -n
cwd=/b/cbuild/shared_internal
Traceback (most recent call last):
  File "/tmp/cbuildbot-tmpx6Wbab/tmpme5b5U/chromite/lib/failures_lib.py", line 172, in wrapped_functor
    return functor(*args, **kwargs)
  File "/tmp/cbuildbot-tmpx6Wbab/tmpme5b5U/chromite/cbuildbot/stages/sync_stages.py", line 890, in PerformStage
    self.ManifestCheckout(new_manifest)
  File "/tmp/cbuildbot-tmpx6Wbab/tmpme5b5U/chromite/cbuildbot/stages/sync_stages.py", line 435, in ManifestCheckout
    self.repo.Sync(next_manifest)
  File "/tmp/cbuildbot-tmpx6Wbab/tmpme5b5U/chromite/cbuildbot/repository.py", line 517, in Sync
    raise SrcCheckOutException(err_msg)
SrcCheckOutException: return code: 2; command: repo --time sync '--cache-dir=/b/cros_git_cache' -n
cwd=/b/cbuild/shared_internal

Build images are missing

Same issue seen with x86-Alex, x86-Alex-he, x-86-zgb, x86-zgb-he

Image building was not started yet. The builder failed to pull code at the very beginning. The build has never worked. I'm wondering who set it up.

+dgarrett, akeshet

I'm reimaging the builder.

./ccompute ri cros-beefy181-c2

PS: For whatever reason, it wasn't updating repo before starting the build. It then passed new commandline options to an old repo command, which died.

If the next build doesn't work, please pass it back.

Last night's build still failed. We're hoping to push dev tomorrow. Do you think this can be fixed today?

It looks like the most recent build passed.

https://uberchromegw.corp.google.com/i/chromeos_release/builders/zako-release%20release-R56-9000.B

Oh... I missed the other boards with the same problem. Reinstancing them now. That should fix the problems.

They've all been reinstanced, which should fix all of the sync problems.