On Thu, Nov 28, 2019 at 05:52:28AM -0500, Ed Maste wrote: > 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 ... Huh. That's weird. You've made sure this is set on *all* the gmake invocations? If you've already built things with NO_VALGRIND=0 they won't get rebuilt. > > 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. Well, I thought I had, but maybe not. I pushed another one today and now I'm seeing a build there. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
