It seems -O options must be delimited by semicolon, not comma

[haplav]

E.g.

-O api=POSIX,collective=no,filePerProc=no;repetitions=4

leads to

Could not load backend API POSIX,collective=no,filePerProc=no

But according to USER_GUIDE, commas should be used.

[JulianKunkel]

Interesting, what do others think? Shall we update the USER_GUIDE or use commas? Am Do., 16. Mai 2019 um 12:05 Uhr schrieb Vaclav Hapla < notifications@github.com>:

…

E.g. -O api=POSIX,collective=no,filePerProc=no;repetitions=4 leads to Could not load backend API POSIX,collective=no,filePerProc=no But according to USER_GUIDE, commas should be used. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#149?email_source=notifications&email_token=ABGW5SVGORCQDG7GDYILKEDPVU5WTA5CNFSM4HNLNQ2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GUEQ3WQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABGW5ST7RYP7QAQCRERMSZTPVU5WTANCNFSM4HNLNQ2A> .

-- Dr. Julian Kunkel Lecturer, Department of Computer Science +44 (0) 118 378 8218 http://www.cs.reading.ac.uk/ https://hps.vi4io.org/ PGP Fingerprint: 1468 1A86 A908 D77E B40F 45D6 2B15 73A5 9D39 A28E

[haplav]

Hm it seems that other than the first option are ignored when using semicolon anyway...

[haplav]

i.e. -O blockSize=3m;api=MPIIO does the same as just -O blockSize=3m

[JulianKunkel]

Thanks for reporting, should be gone now, the bug was introduced with the new option parsing.