fio exits with 0 with some bad job files

If you run fio with --parse-only and a job file such as examples/tiobench-example.fio that's had the semi-colons removed from the first two lines, fio prints an error message but still exits with 0:

% ./fio examples/tiobench-example.fio --parse-only
fio: option <tiobench like setup, add more fX files between the stonewalls to> outside of [] job section
% echo $?
0
%

I'd have expected it to exit with a non-zero value.

Quoted 11 lines · Bruce Cran

If you run fio with --parse-only and a job file such as examples/tiobench-example.fio that's had the semi-colons removed from the first two lines, fio prints an error message but still exits with 0:

% ./fio examples/tiobench-example.fio --parse-only
fio: option <tiobench like setup, add more fX files between the stonewalls to> outside of [] job section
% echo $?
0
%

Quoted 1 line

I'd have expected it to exit with a non-zero value.

Not too surprising, don't think any of that was really audited. But a bug, of course, will look at fixing that up. Is it consistent across any error, or did you just notice this particular one?