<div dir="ltr">Hi,<div><br></div><div>Sorry, I wrote this email at least a month ago, but didn't send it...</div><div><br></div><div>It's not strictly related, but now that the code is fixed, I have copied four of the five OpenCL configs from <a href="http://jenkins.gromacs.org/job/Gromacs_Gerrit_5_1-test-opencl-slave/" target="_blank">http://jenkins.gromacs.org/job/Gromacs_Gerrit_5_1-test-opencl-slave/</a> into <a href="http://jenkins.gromacs.org/job/Gromacs_Gerrit_5_1/" target="_blank">http://jenkins.gromacs.org/job/Gromacs_Gerrit_5_1/</a>.</div><div><br></div><div><div>"Compiler=gcc CompilerVersion=5 GMX_GPU=ON GMX_USE_OPENCL=ON AMDAPPSDK=3.0 CMAKE_BUILD_TYPE=Release host=bs_nix-amd_gpu"</div><div>"Compiler=gcc CompilerVersion=5 GMX_GPU=ON GMX_USE_OPENCL=ON AMDAPPSDK=3.0 GMX_THREAD_MPI=off CMAKE_BUILD_TYPE=Debug host=bs_nix-amd_gpu"</div><div>"Compiler=gcc CompilerVersion=4.7 GMX_GPU=ON GMX_USE_OPENCL=ON CUDA=6.5 GMX_SIMD=SSE4.1 CMAKE_BUILD_TYPE=Debug host=bs_nix1204"</div><div>"Compiler=gcc CompilerVersion=4.8 GMX_GPU=ON GMX_USE_OPENCL=ON CUDA=7.5 GMX_MPI=on CMAKE_BUILD_TYPE=Debug host=bs_nix1310"</div></div><div dir="ltr"><div><br></div><div>So unless e.g. Szilard still wants it, we can delete <a href="http://jenkins.gromacs.org/job/Gromacs_Gerrit_5_1-test-opencl-slave/">http://jenkins.gromacs.org/job/Gromacs_Gerrit_5_1-test-opencl-slave/</a></div><div><br></div><div>Mark</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 6, 2016 at 2:48 PM Szilárd Páll <<a href="mailto:pall.szilard@gmail.com" target="_blank">pall.szilard@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for the explanation!</div><div class="gmail_extra"><br clear="all"><div><div>--<br>Szilárd</div></div></div><div class="gmail_extra">
<br><div class="gmail_quote">On Mon, Jan 4, 2016 at 9:21 PM, Teemu Murtola <span dir="ltr"><<a href="mailto:teemu.murtola@gmail.com" target="_blank">teemu.murtola@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<div><br></div><div>The new pre-submit job output looks nearly identical to the old matrix job (it is still a matrix job). Before it is fully taken into use, you can push changes with "verify-matrix" as their topic, and the new job is also triggered for them; all releng changes currently also trigger both jobs.</div><div><br></div><div>The Jenkins configuration is a bit more complicated with two interconnected jobs, but you will only see the actual matrix linked from Gertit job as long as everything works, with a few caveats:</div><div>* To retrigger a build, you need to navigate to the upstream job instead of using the build linked from Gerrit.</div><div>* If you push changes to the matrix that make it invalid, you will see the non-matrix launcher job getting linked from Gerrit instead of the actual matrix job.</div><div>* And if someone manually aborts the matrix job, there can be some glitches (I think that currently, the build is reported as failed instead of aborted).</div><div><br></div><div>Best regards,</div><div>Teemu<div><div><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 4, 2016, 21:34 Szilárd Páll <<a href="mailto:pall.szilard@gmail.com" target="_blank">pall.szilard@gmail.com</a>> wrote:<br></div><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>Admittedly, I forgot about the pre-submit configs will be stored in the repository. Can we see the output of those tests anywhere? Is the matrix view retained or will it behave like the old "workflow" project's output?</div><div><br></div><div>I'll give a thought to the configs and will review Mark's version when it gets pushed up.</div><div><br></div><div>The comment-based post-submit trigger trigger sounds pretty useful! With this feature, at some future point it may even be useful to allow triggering subset of tests from a the larger collection of e.g. weekly test set.</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div>--<br>Szilárd</div></div></div><div class="gmail_extra">
<br><div class="gmail_quote">On Thu, Dec 31, 2015 at 5:07 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"><p dir="ltr">Hi,</p>
<p dir="ltr">Yes the current pre-submit configuration should be good to go, I tried it out again last week. IIRC I/we thought that letting Gerrit rebase over that content naturally for a few weeks would let us do a clean switch to new Jenkins jobs. I'd been deferring actually doing it until I was back in Stockholm after a month in Australia :-)</p>
<p dir="ltr">I have significant content intended for a post-submit matrix in Gerrit right now (but am reworking it this week). We probably also want to cover some differ combinations in post-submit. </p><span><font color="#888888">
<p dir="ltr">Mark </p>
<br></font></span><div class="gmail_quote"><div><div><div dir="ltr">On Wed, 30 Dec 2015 14:40 Teemu Murtola <<a href="mailto:teemu.murtola@gmail.com" target="_blank">teemu.murtola@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi,<br><br><div class="gmail_quote"></div></div><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Wed, Dec 30, 2015 at 4:11 PM Szilárd Páll <<a href="mailto:pall.szilard@gmail.com" target="_blank">pall.szilard@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div>Unless I'm mistaken, in the current config it's still as simple as adding a new line in the matrix for Gromacs_Gerrit_master-new-releng. However, I'd prefer to not do this based on what I fancy but rather based on what we agree is important.<br></div></div></div></div></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>I'd strongly prefer that we instead start using the configuration in admin/builds/pre-submit-matrix.txt. That also partially solves the problem of agreeing on the things, since the configuration can be discussed in Gerrit before applying any changes. Everything on this front seems to have stopped after <a href="https://gerrit.gromacs.org/5249" target="_blank">5249</a> got merged, though; I don't see why we shouldn't have switched to that a month ago.</div></div></div><div dir="ltr"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Not sure how to add new configs for the post-submit tests. Do we have jenkins project for that? </div></div></div></div></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>There is no post-submit tests, since there is no useful content for them. If people create a set of desired configurations in admin/builds/post-submit-matrix.txt, I can easily create a config that actually builds using it.</div></div></div><div dir="ltr"><div class="gmail_quote"><div><br></div><div>Teemu</div></div></div></div></div><span>
--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" target="_blank">gmx-developers-request@gromacs.org</a>.</span></blockquote></div>
<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" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" target="_blank">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br></div>
--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" target="_blank">gmx-developers-request@gromacs.org</a>.</blockquote></div></div></div></div>
<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" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" target="_blank">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br></div>
--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" target="_blank">gmx-developers-request@gromacs.org</a>.</blockquote></div></div>