<div dir="ltr">For the last week, Jenkins has been silently testing code on the detected SIMD level, not that specified in the command line for the various builds Jenkins spawns. Nobody thought to update the Jenkins configurations for the change from GMX_CPU_ACCELERATION to GMX_SIMD, which I have now done. Canonical re-verify is underway at <a href="http://jenkins.gromacs.org/view/Gerrit%205.0/job/Gromacs_Gerrit_master/4604/">http://jenkins.gromacs.org/view/Gerrit%205.0/job/Gromacs_Gerrit_master/4604/</a><div>
<br></div><div>Sorry,</div><div><br></div><div>Mark</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 18, 2014 at 10:56 PM, Mark Abraham <span dir="ltr"><<a href="mailto:mark.j.abraham@gmail.com" target="_blank">mark.j.abraham@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Lots of changes to the tests are likely to be merged in the next few days, starting now. If you submit patch that is not rebased to HEAD, you will get apparently mysterious complaints from Jenkins. Rebase to HEAD of master and you should be fine, modulo your own problems. As always, please do rebases separately from content changes.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>Mark</div></font></span></div>
</blockquote></div><br></div>