This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/6822] New: Migrate nptl/tst-fork1.c and nptl/tst-fork2.c to test-skeleton.c framework.
- From: "carlos at systemhalted dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 7 Aug 2008 14:04:33 -0000
- Subject: [Bug nptl/6822] New: Migrate nptl/tst-fork1.c and nptl/tst-fork2.c to test-skeleton.c framework.
- Reply-to: sourceware-bugzilla at sourceware dot org
During kernel testing, regression hunting, and experimental patch testing, one
might end up with a system that has bugs in fork. Thankfully the glibc testsuite
reliably catches these bugs, usually exhibited by a hang in nptl/tst-fork1 or
nptl/tst-fork2. The proposed patch enhances the test-skeleton framework to
support running the test function directly without user intervention. This
allows the tests to time out.
The following patch to test-skeleton.c allows a test to force the framework to
run the test function directly, not just with the -direct command line option.
Next we migrate nptl/tst-fork1.c and nptl/tst-fork2.c to the test-skeleton
framework using the new TEST_DIRECT feature. The TEST_DIRECT feature is required
because the tests are testing the fork functionality, and therefore the test
functions can't be forked.
Notes: I have verified that no function leading up to "if(direct)" calls fork.
The obvious brittleness of the test-skeleton framework is that you may
inadvertently try to use a feature before you test said feature. I think being
able to reliably complete a test run outweighs this problem.
Tested on hppa-linux-gnu with no regressions.
Please apply.
--
Summary: Migrate nptl/tst-fork1.c and nptl/tst-fork2.c to test-
skeleton.c framework.
Product: glibc
Version: 2.8
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: carlos at systemhalted dot org
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6822
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.