From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1513 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Unit/regression testing (was Re: [musl] Priorities for next release?) Date: Fri, 10 Aug 2012 15:39:32 -0400 Message-ID: <20120810193932.GC27715@brightrain.aerifal.cx> References: <20120810191254.GA13232@brightrain.aerifal.cx> <50255FA5.2090506@gmail.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1344627529 9195 80.91.229.3 (10 Aug 2012 19:38:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 10 Aug 2012 19:38:49 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-1514-gllmg-musl=m.gmane.org@lists.openwall.com Fri Aug 10 21:38:49 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Szv2m-0002Pk-Jw for gllmg-musl@plane.gmane.org; Fri, 10 Aug 2012 21:38:48 +0200 Original-Received: (qmail 11577 invoked by uid 550); 10 Aug 2012 19:38:47 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 11569 invoked from network); 10 Aug 2012 19:38:47 -0000 Content-Disposition: inline In-Reply-To: <50255FA5.2090506@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:1513 Archived-At: On Fri, Aug 10, 2012 at 12:23:17PM -0700, Nathan McSween wrote: > >Other requests? > > Unit tests of some sort, it helps to document the code as well as > stop some regressions. There are already a number of different tests; see: http://nsz.repo.hu/git/ http://git.etalabs.net/cgi-bin/cgit.cgi https://github.com/lmarcetic/cluts for some that were developed specifically with musl in mind. We've also been using: http://posixtest.sourceforge.net/ but it's rather outdated and incorrect in some areas. I've intentionally kept tests out of the main musl source tree for two reasons: For one thing, I want to avoid burdening non-developers who just want to download musl to use it with unnecessary download/storage bulk. But the other reason is that I want the majority of libc test cases to be libc-agnostic, i.e. designed to run against any libc, not just musl. In that case, including them as part of musl feels wrong. I do however also want to develop some musl-specific regression tests for things that can't be tested in a generic way: things like ensuring that static linking doesn't pull in modules it shouldn't, that unnecessary syscall overhead at startup doesn't creep in, or that musl-specific QoI guarantees are preserved (such as certain interfaces not taking superlinear time or being async-signal-safe even when not required by POSIX). As to how testing relates to this release thread, I think development of further major tests is outside the realm of the immediate sort of release priorities I was asking about. But it's something I've been wanting to pursue again for a long time, and I'd be quite happy to find contributors interested in working on it. Rich