My script has a -j option which is used for both purposes since it does
compilation (also through scons), running the tests, and then validating
the output in different passes.

Is there a way to occupy multiple slots of -t? It might take a new API, but
it is there a way to say, for instance, I can use up an unbounded amount of
parallelism (really something like 900, but that's ~infinite for practical
purposes) and then have the framework say, ok, I'll give you 48 slots since
that's what the user gave me, go for it. Or, here's 12 slots since I want
to run some other stuff at the same time also.

Strictly speaking (without having looked at the code yet), if I hook up all
the system tests through a single invocation of my test running tool (which
is desirable since it filters the global pool of systemc tests somewhat),
then it would take up only one slot of -t accounting wise, but may use a
lot more parallelism/resources than that might imply.

Gabe

On Thu, Jan 17, 2019 at 10:36 AM Jason Lowe-Power <[email protected]>
wrote:

> Hey Gabe,
>
> Right now, there's two parallelism options: -j, which sets the number of
> things to compile simultaneously (just passes it on to scons), and -t which
> specifies the number of different test cases (suites) to run in parallel.
>
> I'd have to dig through the ext/testlib code to point you to exactly where
> the -t option is used, but I think that's what you'd want to use. IIRC,
> Sean also set up things so you could have a remote test server that was
> used to execute parallel tasks. I'm not sure if that was fully plumbed out,
> though.
>
> This might help you get started:
> https://gem5.googlesource.com/public/gem5/+/master/ext/testlib/main.py#269
>
> Cheers,
> Jason
>
> On Wed, Jan 16, 2019 at 4:14 PM Gabe Black <[email protected]> wrote:
>
> > Hi folks. I'm integrating the systemc tests into the testing framework,
> and
> > I wonder what level of parallelism there is in the framework itself, what
> > level of parallelism the tests themselves should utilize, and how that's
> > plumbed down.
> >
> > For instance, I have a verify.py script I wrote to run and verify the
> > systemc tests. It has a lot of nice features that would be difficult to
> > plumb through the framework so I want to keep it as its own independent
> > entity. It has the ability to run scons to build the tests and the tests
> > themselves in parallel which is very useful. I could make it
> automatically
> > detect how much parallelism it might want to use, but that would likely
> be
> > somewhat hard to do in a system dependent way, ie to make it work on macs
> > without having one to test on, and we don't necessarily want it to run as
> > wide as possible regardless of what else might be going on in the system,
> > test wise or otherwise.
> >
> > Is there a way to tell the test framework to do things in parallel? Is
> > there a way to allocate some amount of parallelism at the scheduler level
> > (if a level like that exists) for a particular test, and how is that
> > communicated to the test?
> >
> > Gabe
> > _______________________________________________
> > gem5-dev mailing list
> > [email protected]
> > http://m5sim.org/mailman/listinfo/gem5-dev
> _______________________________________________
> gem5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/gem5-dev
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to