[master] Use parallel instead of xargs

Vratislav Podzimek vpodzime at redhat.com
Thu Jul 24 06:11:33 UTC 2014


On Wed, 2014-07-23 at 08:57 -0700, Brian C. Lane wrote:
> On Wed, Jul 23, 2014 at 11:35:55AM -0400, David Shea wrote:
> > On 07/23/2014 10:35 AM, Vratislav Podzimek wrote:
> > >parallel is a nice utility that can save us a lot of work when running tests in
> > >parallel. By using parallel we can drop things like creating temporary files
> > >with the outputs and failure-flaging.
> > >
> > >Signed-off-by: Vratislav Podzimek <vpodzime at redhat.com>
> > >---
> > >
> > 
> > parallel seems to have some quirks of its own, but in all I like this
> > approach a lot better than xargs. Ack.
> 
> The script should have a test for the presence of the package and fail
> gracefully. xargs is generally (at least on the systems I have)
> installed, but parallel is not.
Yeah, that's a good point. I wanted to add parallel into BuildRequries,
but then I realized we don't even have pylint there.

I'll add that check locally, but maybe we should have some file
documenting which packages are required for running tests. Or what about
running tests in %check and having those files as BuildRequires?

-- 
Vratislav Podzimek

Anaconda Rider | RHCE | Red Hat, Inc. | Brno - Czech Republic




More information about the anaconda-patches mailing list