Skip to content

Make `test -z` more verbose so we can easily catch when it fails

A few of the recent MRs have consistently failed all of their CI tests:

These MRs pass all go tests and vetting when run manually outside of the CI environment. It doesn't seem to matter which runner they are executed on.

Edit: figured out the problem here: test -z "$(go fmt ./...)" was failing, but it's silent on the CI output because it doesn't produce stderr or stdout output. Changing the purpose of this issue from debugging to making sure this doesn't confuse us again.

Edited by Cecylia Bocovich