[PATCH] Updates on busybox POSIX compliance

David Krakov krakov at gmail.com
Thu Jun 18 11:33:48 UTC 2009


Hi,

Table can be updated only manually - documenting differences between
POSIX and busybox behaviour on options that do exist.
It can serve as a mini-TODO file.
The only easy way I see to go with tests is to check for full
compliance by comparing with GNU (which is not strictly compliant
itself).

I ran the test suite - there are some FAILs:
 * Is it up to date?
 * I've seen some tests compare with GNU tools output - does it
require a specific version of GNU utilities?

Though there are tests that can be used for this objective, the test
suite is lacking a simple way to mark existing tests with some kind of
a flag like POSIXTEST. How do you propose to do that?

P.S
attached `runtest -v` stdout and stderr.


On Thu, Jun 18, 2009 at 12:10 AM, Rob Landley <rob at landley.net> wrote:
>
> On Friday 12 June 2009 08:36:41 Denys Vlasenko wrote:
> > On Thu, Jun 11, 2009 at 5:26 PM, Max Panasenkov<panmax at gmail.com> wrote:
> > > Hey,
> > >
> > > Here is some work David and I have done to further improve compliance
> > > table. Please commit them.
> >
> > Committed.
> >
> > I think this file is risking becoming obsolete rather quickly.
>
> The proper thing to do is upgrade the test suite to actually regression test
> POSIX compliance.  Add some kind of POSIXTEST flag to tests (so we know whether
> failing that means something or is just a missing gnu-ism or something), and
> then _the_ test suite can spit out a "Command BLAH passed all posix tests".
> Then run the test suite and grep the results rather than trying to maintain a
> table by hand.
>
> Rob
> --
> Latency is more important than throughput. It's that simple. - Linus Torvalds
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stdout
Type: application/octet-stream
Size: 76351 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20090618/c93e1a0a/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stderr
Type: application/octet-stream
Size: 157 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20090618/c93e1a0a/attachment-0003.obj>


More information about the busybox mailing list