On Sat, May 9, 2015 at 3:19 PM, Bruce Dubbs <[email protected]> wrote: > Douglas R. Reno wrote: >> >> Hi All, >> >> As I am going through my tagging journey, I seem to be having issues >> with the Valgrind test suite. I hear all over the internet that it >> does not work, and I get the following errors out of it (and running a >> "make -k regtest" does absolutely nothing for this) >> >> == 611 tests, 18 stderr failures, 0 stdout failures, 0 stderrB >> failures, 3 stdoutB failures, 2 post failures == > > >> Note that this is with GDB installed only. I am going to install boost >> and llvm next to see if that improves anything. This is more of a >> report than anything else. >> >> I would like to propose that we set the Valgrind test suite to "This >> package does not come with a working test suite" at this point. I have >> also tried the test suite on my GCC 4.9.2 system as well, and I get >> similar results. > > > I think just documenting that 23 tests out of 611 fail would be more > appropriate. Have you looked at why the tests fail? For instance, I notice > from the test names that some seem to need tcl. Do you have tcl installed? > > -- Bruce
I do have TCL 8.6.4 installed, so I do not understand why that one seems to be failing. I just re-ran it as well and I get the same results. I also installed Boost and LLVM as well, since they were mentioned as Optional, and nothing changes. I attempted to examine those tests and I found nothing that was really conclusive. That seems reasonable, I can do that in my next commit (I would prefer that the issue with my commit message not going out in email get fixed before I commit next though). Douglas R. Reno -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
