Sorry, the CI config currently lives in a separate repository. That was originally to allow it to be found & applied for older commits / branches — but I need to move it into the main repo now for future master work: between combining several old files and support for several Rails branches, it’s currently quite tangled.
And to fully clear things out between runs (the MYSQL_IMAGE is particularly sticky):
docker-compose -f .buildkite/docker-compose.yml rm --stop mysql
I just ran the above command to check I had it right, and all the tests were green.
Sorry this process got much uglier. I’ll try to make it better again in future.
This does have me thinking… in retrospect, as we’ve previously seen test incompatibilities between major versions (on all the RDBMSes, at various times), maybe using ‘latest’ is a mistake, and the build config should always use a specific major version. ¯\_(ツ)_/¯
Running Active Record unit test locally against MariaDB 10.4 works like a charm.
I agree that each CI should specify the major version of each RDBMS and look forward that buildkite-config repository takes pull requests to test themselves.