On Wed, 27 Nov 2019 at 03:48, David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> wrote: > > We usually compile valgrind-aware, so that we can run the valgrind > tests without recompiling. You can build with NO_VALGRIND=1 to > suppress that. Pulling the valgrind headers into your FreeBSD > container might be a better idea though. I tried building with NO_VALGRIND w/o success. I tried both setting it in the environment and via gmake NO_VALGRIND=1 ... > Meanwhile, I've been attempting to look at this Cirrus stuff myself > without much luck. I got a Cirrus account with my Github credentials, > and told it to look at the branch, but no builds seem to have appeared > on cirrus-ci.com. Have you pushed to GitHub after allowing Cirrus to see the repository? It won't automatically trigger a build when first granted access to a new repository.
