Joachim Berdal Haga wrote: > Ilmar Wilbers wrote: > >>> Another thing, the buildbots offer an enticing entry "memchecklog", >>> but it >>> seems to be always empty. What's up with that? >>> >>> >>> >> Just like the demolog, it only contains the output of running valgrind >> in case valgrind gives an error. >> > > Right! But it still was empty when it should have failed (the error > upthread). Remember to run it with the flag > > --error-exitcode=<number> [default: 0] > > Specifies an alternative exit code to return if Valgrind reported any > errors in the run. When set to the default value (zero), the return value > from Valgrind will always be the return value of the process being > simulated. When set to a nonzero value, that value is returned instead, if > Valgrind detects any errors. This is useful for using Valgrind as part of an > automated test suite, since it makes it easy to detect test cases for which > Valgrind has reported errors, just by inspecting return codes. > Right... Well, this is set correctly, it is just that the memory checks are disabled in dolfin/test/test.py. I don't know if this should be turned on again, it seems as Ola turned it of three weeks ago: http://fenics.org/hg/dolfin?fl=a286078e0507;file=test/test.py
ilmar _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
