<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">For those that are interested, here is
the MR:<br>
<br>
<a class="moz-txt-link-freetext" href="https://gitlab.com/gromacs/gromacs/-/merge_requests/594">https://gitlab.com/gromacs/gromacs/-/merge_requests/594</a></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">/Paul<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 28/09/2020 17:15, Paul Bauer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKcZa83jp7boDkdQaV+gPJvtUq=YCRiRRV8VgGTKPou43_Fyag@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Hello,
<div dir="auto"><br>
</div>
<div dir="auto">I started to set up tests that can run as jobs
after a commit is merged, and we should just see that we get
this code in to reduce the stress on the hardware. All the
slow jobs can then be moved there.</div>
<div dir="auto"><br>
</div>
<div dir="auto">/Paul</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 28 Sep 2020, 17:00
Erik Lindahl, <<a href="mailto:erik.lindahl@gmail.com"
moz-do-not-send="true">erik.lindahl@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Good point, but it also shows we have some homework to do. Our
new CI infrastructure was quite expanded (~80 high end cores,
2GB/core, all SSD disks) - but this only seems to have led all
of us to happily add tests that took more time.<br>
<br>
Looking just briefly at the pipelines, it seems the testing
phase is our main culprit. While it is of course nice to have
per-change tests, I don't think it's sustainable that we need
10+ CPU hours of testing for every typo fix.<br>
<br>
In particular these tests need attention:<br>
<br>
- gmx-api. They both take 12-15 minutes on two cores, and
there are four of them. <br>
<br>
- TSAN & ASAN. I don't think we can justify using 8 cores
for 15-20 min for each of them.<br>
<br>
- OpenCL, likely related to slow kernel compiles, which gets
even worse when the AMD GPUs become a bottleneck.<br>
<br>
<br>
I also suspect that quite a few tests asking for lots of cores
and memory don't really use all of it (at least not
efficiently), but as a result other CI jobs will have to wait.<br>
<br>
There's also a huge difference in performance between proper
unit tests called on code level vs. the ones that issue
commands or even run simulations.<br>
<br>
This week is not the one to change things, but IMHO we need to
get back to the original model of the CI tests for every
change executing FAST. Any test job that doesn't complete in
less than ~3 min on a single core does not belong among the
ones that are run for every change.<br>
<br>
Cheers,<br>
<br>
Erik<br>
<br>
<br>
<br>
<br>
Erik Lindahl <<a href="mailto:erik.lindahl@scilifelab.se"
target="_blank" rel="noreferrer" moz-do-not-send="true">erik.lindahl@scilifelab.se</a>><br>
Professor of Biophysics<br>
Science for Life Laboratory<br>
Stockholm University & KTH<br>
Office (SciLifeLab): +46 8 524 81567<br>
Cell (Sweden): +46 73 4618050<br>
Cell (US): +1 (650) 924 7674 <br>
<br>
<br>
<br>
> On 28 Sep 2020, at 16:23, Eric Irrgang <<a
href="mailto:ericirrgang@gmail.com" target="_blank"
rel="noreferrer" moz-do-not-send="true">ericirrgang@gmail.com</a>>
wrote:<br>
> <br>
> Hi Devs,<br>
> <br>
> If you push a new commit to a GitLab branch before the
pipelines are finished running for the previous commit, please
consider canceling one or the other sets of pipelines.<br>
> <br>
> You can look at the Pipelines tab of the merge request
page (or just go to <a
href="https://gitlab.com/gromacs/gromacs/-/pipelines"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://gitlab.com/gromacs/gromacs/-/pipelines</a>).
If you have pushed a new commit, you are presumably only
interested in one (of the sets of) pipelines. Just click the
red X to cancel the pipelines you don't need.<br>
> <br>
> If you are pushing to a branch that doesn't have an MR
yet, you are still generating one pipeline for every push, so
please use the web interface to cancel the pipelines that
aren't useful to you.<br>
> <br>
> It will really help all of us to get our CI pipelines to
run sooner.<br>
> <br>
> Thanks!<br>
> M. Eric Irrgang<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 noreferrer" target="_blank"
moz-do-not-send="true">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 noreferrer" target="_blank"
moz-do-not-send="true">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 noreferrer" target="_blank"
moz-do-not-send="true">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" rel="noreferrer" moz-do-not-send="true">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"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">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 noreferrer" target="_blank"
moz-do-not-send="true">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 noreferrer" target="_blank"
moz-do-not-send="true">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" rel="noreferrer" moz-do-not-send="true">gmx-developers-request@gromacs.org</a>.</blockquote>
</div>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Paul Bauer, PhD
GROMACS Development Manager
KTH Stockholm, SciLifeLab
0046737308594</pre>
</body>
</html>