Re: GNU Parallel Bug Reports --joblog parsing fails for commands containing line feeds.

[Coby Viner]

Yes, I agree. Job logs with line feeds within the command were initially generated using GNU Parallel. I created these based upon a more complex GNU Parallel–generated job log using an older version of GNU Parallel.

The script I had which initially generated erroneous job logs, no longer does so as of version 20170522, so this must have been fixed at some earlier point, by instead delimiting line feeds in commands with NULL characters. Therefore, while those old job logs still produce errors in the latest version, the invalid logs themselves are no longer produced when the script is run de novo.

So it appears that this was already effectively resolved! Sorry for the invalid report.

Thanks,

Coby

On Fri, June 23, 2017 2:45 pm, Ole Tange wrote:
> On Fri, Jun 23, 2017 at 7:25 PM, Coby Viner <address@hidden> wrote:
>
>> That command sequence works for me as well, including with the previous
>> version (20170522). It is not, however, equivalent to my case, since
>> when
>> composed in the shell in that manner, the job log stores a command
>> delimited
>> by NULL characters and not by line feeds. It appears to be line feeds
>> themselves which cause the problem, as demonstrated by my previously
>> enclosed log files.
>
> But you did not show how you generated those logfiles. Please do that.
>
> I do not see any reason why you should be able to feed any kind of
> garbage as a joblog file to GNU Parallel: It should accept joblogs
> generated by itself and nothing more. If you can make GNU Parallel
> generate a joblog file that it cannot read or which it reads wrongly,
> then I will consider it a bug.
>
>
> /Ole
>