<div dir="ltr">On Sun, Apr 28, 2013 at 11:44 PM, Frank Loeffler <span dir="ltr"><<a href="mailto:knarf@cct.lsu.edu" target="_blank">knarf@cct.lsu.edu</a>></span> wrote:<div><br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">The currently very scarce results indicate, that at least on one machine<br>
(spine - a Debian workstation, using gcc 4.7) all tests pass. On others<br>
quite some number fail (e.g. supermuc). Common problems seem to be one<br>
Exact testsuite, and some GRHydro suites, especially the new WENO test<br>
stuite. Symmetry thorns also fail some of their tests on more than one<br>
of the four machines.<br>
<br>
As always: failure don't necessarily mean that something is wrong.<br>
Sometimes, the tolerances are just too strict for the underlying code,<br>
and CPUs, different compilers or compiler flags then show these<br>
differences.<br>
<br>
So, in short: the good news is that at least one machine doesn't show<br>
test suite failures, something that was often not the case in the past.<br></blockquote><div><br></div><div style>This is not really news, given that all test cases are run automatically after every commit: <<a href="https://trac.einsteintoolkit.org/">https://trac.einsteintoolkit.org/</a>>; look for "Status". In the past months, we had more problems with repositories (and the automated mechanism itself) than with the Einstein Toolkit code base.</div>
<div style><br></div><div style>-erik</div><div><br></div></div>-- <br>Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a>
</div></div></div>