<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 19, 2013 at 2:34 AM, Szilárd Páll <span dir="ltr"><<a href="mailto:pall.szilard@gmail.com" target="_blank">pall.szilard@gmail.com</a>></span> wrote:<br>
<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"><div class="im">On Wed, Dec 18, 2013 at 11:33 AM, Carsten Kutzner <<a href="mailto:ckutzne@gwdg.de">ckutzne@gwdg.de</a>> wrote:<br>
> Hi,<br>
><br>
> currently the regressiontests that I added for the comp. e-phys<br>
> functionality fail in Jenkins<br>
> (but not on my own machine). I get the following output in Jenkins (for each<br>
> of the tests):<br>
><br>
> Failed<br>
><br>
> complex.swap_x<br>
><br>
> Failing for the past 1 build (Since #3533 )<br>
> Took 0 ms.<br>
> Error Message<br>
><br>
> Erorrs in<br>
> Stacktrace<br>
><br>
><br>
> The raw console output tells me that a .tpr file could not be produced, but<br>
> I cannot see why.<br>
> Where do I find the output produced by grompp?<br>
<br>
</div>The outputs are on the build slaves, so one needs to log in an<br>
manually check them; I grabbed the ones from the following config:<br>
<a href="http://jenkins.gromacs.org/job/Gromacs_Gerrit_master/3533/OPTIONS=Compiler=gcc%20CompilerVersion=4.7%20GMX_GPU=OFF%20CUDA=4.2%20GMX_DOUBLE=ON%20GMX_MPI=OFF%20NRANKS=1%20GMX_CPU_ACCELERATION=SSE4.1%20host=bs_nix1204,label=bs_nix1204/" target="_blank">http://jenkins.gromacs.org/job/Gromacs_Gerrit_master/3533/OPTIONS=Compiler=gcc%20CompilerVersion=4.7%20GMX_GPU=OFF%20CUDA=4.2%20GMX_DOUBLE=ON%20GMX_MPI=OFF%20NRANKS=1%20GMX_CPU_ACCELERATION=SSE4.1%20host=bs_nix1204,label=bs_nix1204/</a><br>
<br>
You can get the tarball from here: <a href="https://db.tt/THnW9JKa" target="_blank">https://db.tt/THnW9JKa</a></blockquote><div><br></div><div>Thanks.</div><div><br></div><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">
Cheers,<br>
--<br>
Szilárd<br>
<br>
PS: couldn't we get the content of .out files to display in the test<br>
result jenkins page? Alternatively, we could copy back some of the<br>
output files to the jeknins server, but this could quickly turn into a<br>
storage challenge.</blockquote><div><br></div><div>My understanding is imperfect, but the readily accessible outputs are stdout/stderr, and those that get sent to an XML file that CTest and/or Jenkins know to deal with (and how).</div>
<div><br></div><div>In principle, we might be able to redirect further content such as the *.out files to fields in the XML files, so that error output can be readily accessed from the web interface. I'm not very keen to invest more time in the perl test harness, though.</div>
<div><br></div><div>Alternatively, Jenkins can probably be told to make certain output files accessible, but maintaining the lists is a bit awkward. Already we have duplication in that CTest knows about the list of regressiontests directories from content in the source repo, and the perl harness has the same list in the regressiontests repo (and I recently reduced some internal duplication there). Jenkins having a magic list of files/globs to preserve would be similarly icky to keep remembering to maintain.</div>
<div><br></div><div>Tarballing the whole workspace automatically (only in case of failure?) could probably be done, not sure how easy maintaining the storage would be.</div><div><br></div><div>Mark</div><div><br></div><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">
<div class=""><div class="h5">
><br>
> 11:14:43 Abnormal return value for 'gmx grompp -maxwarn 10 -n index<br>
>>grompp.out 2>&1' was 255<br>
> 11:14:43 No topol.tpr file in swap_x. grompp failed<br>
> 11:14:43 FAILED. Check files in swap_x<br>
><br>
> Thanks,<br>
> Carsten<br>
> --<br>
> Gromacs Developers mailing list<br>
><br>
> * Please search the archive at<br>
> <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before<br>
> posting!<br>
><br>
> * Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
><br>
> * For (un)subscribe requests visit<br>
> <a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or<br>
> send a mail to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br>
--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br>
</div></div></blockquote></div><br></div></div>