> -----Original Message-----
> From: Gabe Black <[email protected]>
> Sent: 12 October 2021 10:28
> To: Giacomo Travaglini <[email protected]>
> Cc: gem5 Developer List <[email protected]>
> Subject: Re: [gem5-dev] reduce the number of checkpoints in the ARM
> checkpoint test?
>
> Hi Giacomo. it's definitely minutes, probably between 5 and 10 per
> checkpoint.

I see

>
> Another thing I noticed is that often, the test infrastructure will schedule 
> the
> typically two final and longer running tests (I think both ARM boot tests) at
> the same time, but sometimes I'll wait and wait for the checkpoint one to run,
> and then it will start the other ARM test serially after it, even though I 
> passed
> in -t 6 (run 6 tests in parallel). It's just a guess, but is the framework 
> setting up
> 6 static schedules of tests and then feeding them to 6 threads to run? Or is 
> it
> dynamically scheduling them based on when different threads finish their
> current task? If it's the first, I think the second would be a great
> improvement as well, since that will save the occasional unnecessary
> serialization of long running tests.

As far as I can see we are using the multiprocessing.Pool object [1] which 
means a worker process
Will be used as soon as it becomes available. There shouldn't be dependencies 
between linux boot tests, except
For the regex matching tests which complete in almost zero time

>
> Gabe
>

Kind Regards

Giacomo

[1]: https://github.com/gem5/gem5/blob/stable/ext/testlib/runner.py#L177
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
gem5-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to