At 3:02 AM +0200 11/21/03, Saku Setala wrote: >t/IO/OPENPID....ok >All tests successful. >u=409.85 s=0 cu=0 cs=0 scripts=1 tests=10 > >Strange?
If it fails in the test suite but then succeeds when run individually, it usually means the problem was not in whatever the test was designed to verify. It could be a quota issue of some kind. For example, since signal handling was involved in this test, it might be ASTLM. Or, since all the tests are run through pipes, which are significant users of BYTLM, that could be the issue. Or it could be a bug in the test driver or various other things that are hard to track down. Or the test might unwittingly make assumptions about the relative timing of certain events such that it usually works on fast processors but not on slow/busy ones. If you have the time and the interest and can turn this into something reproducible, it would of course be good to nail down. There may be very little payback, though, unless you are able to isolate an as yet unknown bug. Thanks again for the report. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
