Why do you need to run this tryjob? Maybe Don intentionally dropped support for this.

To test master-paladin on remote tryjobs. Without --buildbot, CQ specific stages (like CommitQueueSyncStage or CommitQueueCompletionStage) won't be run.

I'm thinking that that's the real bug. --buildbot shouldn't matter.

I have a stack of changes that will create master-paladin-tryjob when they are finished. Long term, we should make that build config as useful as it can be for doing these kinds of tests.

I'll fiddle and see if I can come up with a solution until then.

I suggested this earlier, but nxia@ said it wasn't working..... but seems to work for me.

Change to the directory that contains the changes you want to test, and run:

  cbuildbot --debug --buildbot --nobootstrap --noreexec --buildroot <dir> <config>


It runs locally, and you can't keep using that checkout while it runs, but it should test your changes.

Ah... it did eventually die.

AssertionError: No database connection to use.

any updates on the tryjobs?

Some of the CLs are in, but not all. And there is a plan (your) to make this work in general.

Implementation is in-progress.

I believe this now works.

cros tryjob --production --debug.