Re: T.chroot 4 (was: FIP test results)
Mats,
There was a thread on this back in March.
http://lists.debian.org/lsb-test/2002/lsb-test-200203/msg00104.html
Here is a note from Andrew Josey. Subject: Re: T.chroot 4 Date: Fri, 29
Mar 2002 15:13:48 GMT
This is a known feature with the test suite, hence the FIP result
code, which is encountered on systems using shared libraries.
Upon performing the chroot() call the shared library is no longer
accessible and the process terminates. The FIP code is not a
failure but requires manual inspection.
We may want to look at changing the output/result code so
we can avoid the manual inspection .
regards
Andrew
Kevin Caunt
krc@us.ibm.com
512-823-8540; t/l 793-8540
IBM Linux Technology Center
FSG's Linux Standard Base
"Wichmann, Mats D" <mats.d.wichmann@intel.com> on 07/30/2002 04:02:43 PM
To: lsb-test@lists.linuxbase.org
cc:
Subject: T.chroot 4 (was: FIP test results)
Anybody know what the story is with T.chroot 4?
It's FIP on every test run I have because the
test is "not found"
execv() of ./t.chroot_4 - errno 2 (ENOENT)
I've never really paid attention to this,
since I'm not signing off a test run for
certification, but why isn't this working?
Presumably, it's expected since otherwise it
would show as a FAIL... what are we
signing off on if we sign off this one?
Curious...
Mats
--
To UNSUBSCRIBE, email to lsb-test-request@lists.linuxbase.org
with subject of "unsubscribe". Trouble? Email
listmaster@lists.linuxbase.org
Reply to: