<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 class="gmail_signature">--<br>Szilárd</div></div>
<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 class="HOEnZb"><font color="#888888">
<p dir="ltr">Mark </p>
<br></font></span><div class="gmail_quote"><div><div class="h5"><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 class="h5"><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 class="">
--<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">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br></div>