|
From: Tom H. <th...@cy...> - 2004-02-28 17:16:58
|
In message <E1A...@au...> you wrote: > == 126 tests, 12 stderr failures, 0 stdout failures ================= > corecheck/tests/fdleak_cmsg (stderr) > corecheck/tests/fdleak_creat (stderr) > corecheck/tests/fdleak_dup (stderr) > corecheck/tests/fdleak_dup2 (stderr) > corecheck/tests/fdleak_fcntl (stderr) > corecheck/tests/fdleak_ipv4 (stderr) > corecheck/tests/fdleak_open (stderr) > corecheck/tests/fdleak_pipe (stderr) > corecheck/tests/fdleak_socketpair (stderr) > helgrind/tests/inherit (stderr) > massif/tests/true_html (stderr) > massif/tests/true_text (stderr) The fdleak_ failures are caused by the overnight tests being run from cron and getting /dev/null as standard input which is explicitly left alone by the filter script and hence the output doesn't match the expected results which are designed for running from a terminal where the terminal name would get filtered out. The helgrind inherit test is as I mentioned in the RH8 results, and the massif failures have already been discussed and have an open bug. Tom -- Tom Hughes (th...@cy...) Software Engineer, Cyberscience Corporation http://www.cyberscience.com/ |