[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HP compute nodes ; Is GNU parallel executing files in parallel?

From: Ole Tange
Subject: Re: HP compute nodes ; Is GNU parallel executing files in parallel?
Date: Wed, 28 Jun 2017 03:57:30 +0200

On Tue, Jun 27, 2017 at 9:34 PM, Anukesh K A <> wrote:

> Hi,
> My name is Anukesh

Hi Anukesh

Thanks for your report.

Unfortunately I have not been able to reproduce the behavior you see:
Amongst other things I do not have access to

Luckily there is a procedure that has proven to speed up finding a
solution. This procedure is described in the section on Reporting Bugs
in the man page:


Report bugs to <> or

See a perfect bug report on

Your bug report should always include:

* The error message you get (if any).

* The complete output of parallel --version. If you are not running
the latest released version (see you
should specify why you believe the problem is not fixed in that

* A minimal, complete, and verifiable example (See description on It should be a complete example
that others can run that shows the problem including all files needed
to run the example. This should preferably be small and simple, so try
to remove as many options as possible. A combination of yes, seq, cat,
echo, and sleep can reproduce most errors. If your example requires
large files, see if you can make them by something like seq 1000000 >
file or yes | head -n 10000000 > file. If your example requires remote
execution, see if you can use localhost - maybe using another login.

* The output of your example. If your problem is not easily reproduced
by others, the output might help them figure out the problem.

* Whether you have watched the intro videos
(, walked
through the tutorial (man parallel_tutorial), and read the EXAMPLE
section in the man page (man parallel - search for EXAMPLE:).

If you suspect the error is dependent on your environment or
distribution, please see if you can reproduce the error on one of
these VirtualBox images:

Specifying the name of your distribution is not enough as you may have
installed software that is not in the VirtualBox images.

If you cannot reproduce the error on any of the VirtualBox images
above, see if you can build a VirtualBox image on which you can
reproduce the error. If not you should assume the debugging will be
done through you. That will put more burden on you and it is extra
important you give any information that help. In general the problem
will be fixed faster and with less work for you if you can reproduce
the error on a VirtualBox.


Hope this will get you further.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]