On Fri, Oct 23, 2020 at 1:46 PM Jürg Billeter <[email protected]> wrote:
> Hi Justin, > > On Fri, 2020-10-23 at 12:52 -0400, Justin Erenkrantz wrote: > > How should downstream projects think about conducting build tests > > (eg, 'make check', etc, etc)? > > > > In particular, we've been working on bringing Buildstream to Apache Serf > > (which is an HTTP client library)[1]. Our current test suite requires > > network access - it brings up a mock HTTP server and then runs test cases > > with the local builds. > > A private loopback network is available in Bubblewrap sandboxes. I.e. > as long as the mock HTTP server is brought up on localhost in the same > BuildStream sandbox as the client tests, I expect this to work. Or have > you encountered any issues with this? > > Issues related to running tests in BuildStream: > * https://gitlab.com/BuildStream/buildstream/-/issues/776 > * https://gitlab.com/BuildStream/buildstream/-/issues/1327 Thanks for the pointers. When we have cycles to pick up the Buildstream integration for serf, we'll keep these issues in mind. >From a development standpoint, we often need to be able to test against actual servers in case we can't reproduce over localhost. I guess that we could export the build artifacts from the sandbox and run them locally...I'd have to think about what the workflow would look like...we'd often want to jump into a debugger which needs the objects and source paths - so, I don't think it's necessarily straightforward. Or, am I missing a trick here? Cheers. -- justin
