[gmx-developers] master post-submit breakage

[Mark Abraham]

Hi,

Yes the jobs can be triggered manually with specific refspecs, just as it
ever did. Probably best to trigger the main pipeline job, not the matrix
one.

Mark

On Thu, 28 Sep 2017 18:30 Schulz, Roland <roland.schulz at intel.com> wrote:

> Hi,
>
>
>
> Is it possible to trigger the post submit job for a specific hash/refspec?
> I would be surprised if the issue isn’t because of b9057925955f066. I tried
> to trigger for refs/changes/20/6720/8 (refspec of parent) but it didn’t
> build any configurations.
>
>
>
> Roland
>
>
>
> *From:* gromacs.org_gmx-developers-bounces at maillist.sys.kth.se [mailto:
> gromacs.org_gmx-developers-bounces at maillist.sys.kth.se] *On Behalf Of *
> Mark Abraham
> *Sent:* Thursday, September 28, 2017 7:29 AM
> *To:* Discussion list for GROMACS development <gmx-developers at gromacs.org>
> *Subject:* Re: [gmx-developers] master post-submit breakage
>
>
>
> Hi,
>
>
>
> Agreed. I just don't know how to make it work well.
>
>
>
> Obviously Redmine exists for its purpose :-)
>
>
>
> Mark
>
>
>
> On Thu, Sep 28, 2017 at 4:15 PM Szilárd Páll <pall.szilard at gmail.com>
> wrote:
>
> Hi,
>
>
>
> I think it's identifying that there is an issue to fix and having a record
> of that that somewhere is quite important (so that someone else noticing
> failing post-submit can go somewhere to check for known issues).
>
>
>
> Recording known issues and with the commit or date/CI infrastructure
> change that triggered it would also be helpful for the unavoidable case of
> compoound post-submit failure scenarios.
>
>
>
> Therefore, unless we have a clear way to track in Jenkins what and when
> broke as well as new breakage, I filing redmine a issue(s) still seems the
> best option.
>
>
>
> Cheers,
>
>
> --
> Szilárd
>
>
>
> On Thu, Sep 28, 2017 at 4:05 PM, Mark Abraham <mark.j.abraham at gmail.com>
> wrote:
>
> Hi,
>
>
>
> Relevant are that we have had some recent fixes for ARM, and some more
> sensitivity for SIMD tests, and some changed maths implementations, and
> maybe the merges from release-2016. The last reported successful build (and
> its neighbours in the commit history) does not suggest anything to me
> (neither releng history), but we have had several issues leading to
> failures in post-submit, and some of them were happening at the same time.
>
>
>
> Policy is that if we identify what patch caused an issue and there's no
> fix available, then we will revert so that we don't get into the
> multiple-failures quagmire. However that means we need people to be
> vigilant about fixing issues in their code, and reviewing those fixes. Some
> email alerts would be good, but I haven't seen any. Please see what you
> find!
>
>
>
> Mark
>
>
>
> On Thu, Sep 28, 2017 at 3:03 PM Szilárd Páll <pall.szilard at gmail.com>
> wrote:
>
> Hi,
>
>
>
> Some SIMD and math unit test have been broken for about a month. A quick
> search have not showed any redmine issue on this. Is anybody aware of the
> issue, perhaps working on fixing it? Can we have a redmine?
>
>
>
> Additionally, especially if this has gone ignored (or worse unnoticed) for
> a month, we to instate a notification mechanism. I'm not sure authors of
> upstream triggers can be correctly detected in matrix jobs, but I'll enable
> some options and we shall see.
>
>
> Cheers,
>
> --
> Szilárd
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
>
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
>
>
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20170928/01bf249e/attachment.html>