This is WAI: http://cs/chromeos_public/chromite/config/COMMIT-QUEUE.ini?l=10&rcl=f8268f7ccb655e300527e2374056fb3b4be1a658 . It ran tests in PreCQ and submitted because they had already passed.

I think that the setup is correct until we move most of the configuration to be database-based instead of config-file-based. Once that's done, config changes will also be instantaneous.

Our system today isn't smart enough to detect that your change affected a CQ builder specifically, it only looks at the directory the files are in.

Build config changes are submitted from the PreCQ because of chances of conflicts and rebase problems in config_dump.json are so high, and quick submission helps avoid them.

Generally speaking, that's been a win.

Got it, thanks! It looks like the Tast suites were passing at the time of the change being committed, so hopefully no harm done. I'll keep this in mind when making future changes to paladin configs.

I think this is the first bug I've gotten saying a CL was submitted too quickly. ;>