parallel
[Top][All Lists]
Advanced

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

Re: GNU Parallel Bug Reports Error after update in server


From: Ole Tange
Subject: Re: GNU Parallel Bug Reports Error after update in server
Date: Wed, 14 Aug 2013 01:41:34 +0200

On Tue, Aug 13, 2013 at 6:06 PM, Maria Evangelia Chatzimina
<hatziminamaria@gmail.com> wrote:
> Hello.
> I have a problem after an update in the server I was using parallel
> The error is
> parallel: Error: -g has been retired. Use --group.
> parallel: Error: -B has been retired. Use --bf.
> parallel: Error: -T has been retired. Use --tty.
> parallel: Error: -U has been retired. Use --er.
> parallel: Error: -W has been retired. Use --wd.
> parallel: Error: -Y has been retired. Use --shebang.
> parallel: Error: -H has been retired. Use --halt.
>
>
> I don't use -g,-B etc and also I have removed --tollef
> Please help :(
> Thank you very much
> Maria

>From man parallel:

REPORTING BUGS

       Your bug report should always include:

       · The error message you get (if any).

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

       · A complete example that others can run that shows the problem. This
         should preferably be small and simple. 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.

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

       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:
       http://sourceforge.net/projects/virtualboximage/files/

       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, 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.

Based on the very limited information you provide, I think it is due
to your environment. So please try to see if you can reproduce it on
one of the VirtualBox images mentioned above.

Also post the output of:

  strace -ff parallel ::: true

/Ole



reply via email to

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