On 14/06/07 11:38, John Scoles wrote:
seems this is a bug in the code when dealing with Solaris. So I would
just ignore it for now
here is a link to it
http://www.nntp.perl.org/group/perl.dbi.dev/2006/01/msg4401.html
The above URL points to a posting of mine in which I report a
bug in the the test suite, and provide a fix. This fix was
incorporated into the released version of DBI 1.50.
It is the fixed test which is now failing. As the code says,
the purpose of the test is
# basic check that we can fork subprocesses and wait for the status
t/10general.............NOK
1
# Failed test 'system exit 1 should return 256'
# in t/10general.t at line 31.
# got: '-1'
# expected: '256'
t/10general.............NOK
2
# Failed test 'system exit 0 should return 0'
# in t/10general.t at line 32.
# got: '-1'
# expected: '0'
The result of the test suggests that we cannot Fork subprocesses
and wait for the status. 'perldoc -f system' says:
Return value of -1 indicates a failure to start the program
(inspect $! for the reason).
Something is very seriously wrong if system('exit 0;') is failing.
I am afraid I do not have the time to investigate this myself at
the moment, but it does need investigating. A good start would be
to modify the test to print the value of $! after the failure.
--
Charles Jardine - Computing Service, University of Cambridge
[EMAIL PROTECTED] Tel: +44 1223 334506, Fax: +44 1223 334679
