public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Geoff Gustafson" <geoff@linux.co.intel.com>
To: <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Open POSIX Test Suite
Date: Mon, 4 Nov 2002 14:48:47 -0800	[thread overview]
Message-ID: <000a01c28454$56a94b90$7fd40a0a@amr.corp.intel.com> (raw)

I would like to announce a new project to develop and/or assemble a GPL test
suite for POSIX APIs. The tests will focus on conformance to the IEEE Std
1003.1-2001, but will also include separate functional and stress tests.

The project's current approach to conformance testing is to record
assertions
from a close reading of the POSIX specifications, and write minimal test
cases
that prove or disprove these assertions. The test suite will be independent
of
specific API implementations, and will eventually be easily configurable to
work with different implementations. The project aims for OS independence,
using only POSIX APIs, the autoconf suite, and simple shell support.
However,
it is currently only being tested on Linux.

Ultimately, the plan is to use the test suite to evaluate current support in
Linux, as well as new implementations being considered in the open source
community, and then contribute patches or at least bug reports (with a
minimal
test case) to the appropriate places, like LKML.

Contributions of any test cases, review of the work, discussion of the
approach, etc. are very welcome. Join the development mailing list,
posixtest-discuss. The initial focus is on Signals, Message Queues, Threads,
Semaphores, and Clocks & Timers, based on current interests and resources.
You can help in these areas, or start work on another area of the spec.
There
will need to be some uniformity across the suite, but many details have yet
to
be worked out, so your involvement in those decisions help a lot.

For more information, see the project website at
http://posixtest.sourceforge.net

Thanks,

-- Geoff Gustafson

These are my views and not necessarily those of my employer.


             reply	other threads:[~2002-11-04 22:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 22:48 Geoff Gustafson [this message]
2002-11-04 22:58 ` [ANNOUNCE] Open POSIX Test Suite Larry McVoy
2002-11-04 23:17   ` Geoff Gustafson
2002-11-04 23:14 ` RFC: A POSIX Linux project? Jeff Garzik
2002-11-04 23:31   ` Andreas Dilger
2002-11-04 23:51     ` Jim Freeman
2002-11-05  0:14       ` Geoff Gustafson
2002-11-05  2:01     ` Geoff Gustafson
2002-11-04 23:37   ` Rik van Riel
2002-11-05  1:14   ` Geoff Gustafson
2002-11-04 23:57 ` [ANNOUNCE] Open POSIX Test Suite Christopher Yeoh
2002-11-05  0:44   ` Geoff Gustafson
2002-11-05  2:26     ` Andreas Dilger
2002-11-05  3:35     ` Christopher Yeoh
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04 23:29 Dan Kegel
2002-11-05  0:04 ` Geoff Gustafson
2002-11-05  0:08   ` Dan Kegel
2002-11-05  0:24   ` Dan Kegel
2002-11-05  3:18     ` Christopher Yeoh
2002-11-05 15:44   ` Nathan Straz
2002-11-05 15:49 Stephanie Glass
2002-11-05 16:43 ` Rusty Lynch
2002-11-05 18:24 Stephanie Glass
2002-11-05 19:05 ` Rusty Lynch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000a01c28454$56a94b90$7fd40a0a@amr.corp.intel.com' \
    --to=geoff@linux.co.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox