[Fuego] LTP test split - was RE: Wiki docs for 1.3 release

Tim.Bird at sony.com Tim.Bird at sony.com
Thu Mar 29 01:42:25 UTC 2018

> -----Original Message-----
> From: Daniel Sangorrin
> > -----Original Message-----
> > From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-
> bounces at lists.linuxfoundation.org] On Behalf Of Daniel Sangorrin
> > > My idea is to figure out a mechanism to share the build directory, so that
> > > the host is not duplicating  1G of build space for each sub-test.  Any ideas
> > > for this are appreciated.  We have sharing of build instructions and source
> > > for netperf, OpenSSL and rt-tests, but I don't think we share the build
> > > directories for these, when they are used by different tests (e.g
> > > Benchmark.netperf vs. Functional.netperf).
> >
> > I like this idea.
> >
> > Tests sharing the same build folder could specify the build folder name
> > with a special variable (BUILD_DIR="sharedbuildfolderforrttests"), then
> > Fuego would also append the "-$ARCH" suffix and build there.
> > These tests should be sharing the same "test_build" function. And the
> > test_build function should build the binaries necessary running all tests.
> Looking at the code, it looks that it could be as easy as overwritting
> on the pre_build function.
> Do you want me to try it with the rt-tests?

Sure.  Give it a whirl.

I think the basic idea is for a "sub-test" of LTP to do the following:
1) check if there's an already existing build of LTP, and use that
2) if there's not an already existing build, then do a build of LTP.
  we might be able to do something like this:
   "ftc run-test -b $NODE_NAME -t Functional.LTP -p  pcb"
and not have to copy build instructions from LTP

I have no idea if nested job execution like this will work or not.

 3) just refer to Functional.LTPs build directory, as you say above.

 -- Tim

More information about the Fuego mailing list