[Fuego] [LTSI-dev] First post, LTSI TEST questions

[Bird, Timothy]

> -----Original Message-----
> From: Doug Crawford [mailto:dcrawford at zonoff.com]
> Sent: Wednesday, September 21, 2016 11:34 AM
> To: Bird, Timothy <Tim.Bird at am.sony.com>
> Cc: ltsi-dev at lists.linuxfoundation.org; fuego at lists.linuxfoundation.org
> Subject: Re: [LTSI-dev] First post, LTSI TEST questions
> 
> 
> > On Sep 20, 2016, at 8:23 PM, Bird, Timothy <Tim.Bird at am.sony.com> wrote:
> >
> >> -----Original Message-----
> >> From: ltsi-dev-bounces at lists.linuxfoundation.org [mailto:ltsi-dev-
> >>
> >> Our systems team is evaluating if the LTSI test system might be applicable to
> our
> >> kernel QA process.
> >> If so we would be pleased to be users and perhaps, in time, contributors.
> >>
> >> Is there a catalog of the “60+” tests currently in the LTSI Test System that
> >> documents the details of what each test accomplishes?
> >
> > Unfortunately, no.  Each test is supposed to come with a description field
> > filled in (in it's config.xml file).  But I was recently examining them, and the
> > descriptions are often missing, and sometimes quite minimal.  IMHO this is
> > something we should really fix up.
> >
> > One feature I'd like to add to the command line tool (which is under
> construction
> > at the moment) is the ability to list the descriptions in a kind-of catalog form,
> > so people can peruse these more easily.
> >
> > And finally, I'm hoping in the very long term to put each test in it's own
> package,
> > and have such information easily accessible via a standard package manager
> tool.
> >
> > Sorry - I know this doesn't help you in your evaluation in the short term.
> >
> >> Thanks very much in advance!
> >
> > Thanks for taking the time to evaluate the tool.  As we receive feedback from
> people
> > it helps us prioritize the things we're working on.
> > -- Tim
> >
> 
> Tim:
> Thanks so much for the heads up.  I appreciate you mentioning the plans for
> providing content info.
> I will continue to work through getting the system running.
> In the mean time, can you point me to the source files for the tests themselves?

The tests consist of multiple files, but the main "base script" for each test, which
is the one that builds the source, deploys it to target, executes it and collects
and analyses the result is in each test's "home" directory under /home/jenkins/tests
(inside the container).

So, for example, the base script for bonnie is in /home/Jenkins/tests/Benchmark.bonnie,
and is called bonnie++.sh

See http://bird.org/fuego/Adding_a_test#Files for a description of the different files
that are part of a test definition, and where they are in the system (inside the container).

Because there are symlinks, you can find the files via multiple paths:
/home/jenkins/tests/{test_name}
or
/home/jenkins/fuego/engine/tests/{test_name}

Note that /home/jenkins/fuego corresponds to the git repository fuego-core.
(See https://bitbucket.org/tbird20d/fuego-core/)

> I looked around, expecting to find .c or .cpp files within the jaa-public directory
> and the docker volume, no luck.
> Perhaps these come in on a further installation step, but I don’t seem to see that
> happening in
> the steps of the jta document pdf.

It sounds like you're using jta instead of fuego (and an older version of jta at that).
You might want to try using fuego instead, from this repository:
https://bitbucket.org/tbird20d/fuego/

I'm not sure how far behind fuego jta is, but jta is deprecated now.
 -- Tim