On Mon, Oct 22, 2012 at 9:00 AM, Andrey Ponomarenko
<aponomarenko@rosalab.ru> wrote:
I've recently written an article [1] about smoke testing of Glibc API using
a modern approach. This kind of test is needed to verify that most of the
library functions pass a simple test in the particular environment, i.e.
don't crash, don't emit any signal, don't hang and don't exit with non-zero
error code. The test generator takes only a path to the installed glibc tree
in order to compose input arguments for all functions (reasonable in most,
but unfortunately not all, cases) and then create, build and run the test
cases.
I've added a link to this article on the Release Process page (section 5.6.
Testing), so that glibc maintainers can run this additional test when
preparing the release and look at the behaviour of all functions under the
smoke test. The sample test report for 2.16 looks like this one [2].
Andrey,
Thanks! This looks very interesting.
Will you continue to work on getting these results clean for glibc?
Going through 154 failed testcases from the smoke test is not something
that I want a release manager to be doing.