Date: Tue, 28 Feb 2023 20:50:15 +0800 From: Li-Wen Hsu <lwhsu@freebsd.org> To: Alexander Leidinger <netchild@freebsd.org> Cc: jenkins-admin@freebsd.org, dev-ci@freebsd.org Subject: Re: FreeBSD-main-amd64-test - Build #23067 - Still Unstable Message-ID: <CAKBkRUw324Mx42Sex3gmq5MdBxULwdrJ-rzpB61GPpk03Aqwvw@mail.gmail.com> In-Reply-To: <20230228133931.Horde.xmkg4eSQvayaSfv4mzJ8TxY@webmail.leidinger.net> References: <1135435580.10757.1677573565464@jenkins.ci.freebsd.org> <309792743.10759.1677585266472@jenkins.ci.freebsd.org> <20230228131850.Horde.s0MSig5KCxiS5lgMljHsq7B@webmail.leidinger.net> <CAKBkRUykov2vZXwxyc%2BLBJp0iYNVs-GdrF0%2B5z7UNuq=KXhvmg@mail.gmail.com> <20230228133931.Horde.xmkg4eSQvayaSfv4mzJ8TxY@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 28, 2023 at 8:39=E2=80=AFPM Alexander Leidinger <netchild@freebsd.org> wrote: > > Quoting Li-Wen Hsu <lwhsu@freebsd.org> (from Tue, 28 Feb 2023 20:21:46 +0= 800): > > > Please check "Status explanation" part of the first message. > > Ok. Thanks. > > Wouldn't it make sense to send emails on failure and fix instead of > failure and "still failure"? Sounds a little bit of overkill to send > mails to unrelated commits. Maybe a periodic reminder to the original > commit when it is not fixed... > > Obviously it creates misunderstandings in the current way. > That does make sense, but unfortunately currently it's not easy to tell the cause of "still unstable" is because of the previous error, or previous error along with the new error. Yes I know a script to process and integrating to the system is possible to solve this, but I'm still working higher priorities TODO items... Best, Li-Wen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKBkRUw324Mx42Sex3gmq5MdBxULwdrJ-rzpB61GPpk03Aqwvw>