mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Missing tests
Date: Wed, 14 May 2014 16:30:46 +0200	[thread overview]
Message-ID: <20140514143046.GU12324@port70.net> (raw)
In-Reply-To: <20140514130530.GA6999@brightrain.aerifal.cx>

* Rich Felker <dalias@libc.org> [2014-05-14 09:05:30 -0400]:
> Here are some things that don't seem to be tested that would be nice
> to get added to the test suite (http://nsz.repo.hu/git/?p=libc-test)
> 
> - Interpretation of POSIX TZ strings
> - Daylight time transition tests with zoneinfo and POSIX zones
> - Lots of corner cases for strftime and strptime
> - Regression test for recent pthread_once race (hard to catch)
> - Sanity-checking ucontext_t layout via signal handlers
> - Alternate signal stacks
i have a (regression) test for sigaltstack

> - Basic sanity checks for most syscalls
this can be tricky

> It might make sense to make a new tree separate from functional for
> tests that don't really check the functionality of the interface but
> just whether it's present and "doing something". Some existing tests
> might be candidates for moving there too..?

the code organization is not optimal

we can add a directory for trivial tests

the difficult part is when the test needs special environment
(eg syscall sanity checks or getaddrinfo): users/groups,
root-priv, fs-access, /etc/ changes,...
we can collect them in separate dirs and run only
when in a completely isolated environment (eg qemu)

linux specific tests should be separate too

another todo item is to improve cross compilation
(running cross compiled tests does not really work
now because it is done from make)
(the dso tests are a bit broken too because they use
relative path so only work when started from a specific
dir, maybe such test should be started from an .sh script)


  reply	other threads:[~2014-05-14 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 13:05 Rich Felker
2014-05-14 14:30 ` Szabolcs Nagy [this message]
2014-05-20 19:49   ` Rich Felker

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=20140514143046.GU12324@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).