incorrect value expected in /tset/LSB.os/genuts/getopt/T.getopt 4

[Jeff Johnson]

The expected value doesn't match the actual output for years. Maybe it would be
worth of an update...

notes from bug 3851:

Karel Srot 2013-09-12 15:23:51 UTC

Similar case is the FIP test /tset/LSB.os/genuts/getopt/T.getopt 4

getopt() : Possibly incorrect diagnostic output to standard error:-
Expected diagnostic output :-
 pname: illegal option -- a
Actual diagnostic output :-
 pname: invalid option -- 'a'
getopt() : Possibly incorrect diagnostic output to standard error:-
Expected diagnostic output :-
 pname: option requires an argument -- a
Actual diagnostic output :-
 pname: option requires an argument -- 'a'

This one is also appearing at least since 2010.

[reply] [-] Comment 4 Mats Wichmann 2013-09-12 15:46:41 UTC

This sounds like a separate incident, although you could argue it's related in
the sense of "improperly expecting a specific string".

The test purpose documentation claims this:

          4 The formats of the diagnostics printed to standard
               error by a call to getopt() in the POSIX locale are as
               follows:
               "%s: illegal option -- %c\n", <program name>, <option
               character>
               "%s: option requires an argument -- %c\n", <program
               name>, <option character>

I don't have any idea where that comes from, as I see nothing in POSIX that
specifies the format or content of a diagnostic error written to stderr, merely
that it may happen. The test is in the LSB.os area, which means it was written
specifically for LSB; presumably somebody just did research on what the
messages were at that time.