From: "Frank Ch. Eigler" <fche@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>, bunsen@sourceware.org
Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs
Date: Tue, 16 Jan 2024 12:10:17 -0500 [thread overview]
Message-ID: <20240116171017.GH26700@redhat.com> (raw)
In-Reply-To: <CAPS5khZ0N76F=mzbZZAQeYjhJuh9h26w+KiDTox8KVYBKjfWDQ@mail.gmail.com>
Hi -
> > Interesting. In the bunsen model, that would be better represented as
> > individual testrun commits for each of the run attempts, including the
>
> Do you mean each testrun includes the whole testsuite?
Each testrun includes just as much of the testsuite as you wish.
> In our case, only the first run includes the whole testsuite, the
> subsequent ones include only the .exp files for which we detected
> failures, to keep testing time reasonably low.
That makes sense (unless you get a false positive PASS in the first
run, don't bother rerun, and miss the flake!). In any case, bunsen
would gladly accept the logs generated from each of the partial
reruns.
- FChE
next prev parent reply other threads:[~2024-01-16 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 18:50 Frank Ch. Eigler
2023-12-14 15:45 ` Maxim Kuvyrkov
2024-01-02 22:13 ` Frank Ch. Eigler
2024-01-03 12:59 ` Maxim Kuvyrkov
2024-01-04 2:34 ` Frank Ch. Eigler
2024-01-11 13:42 ` Maxim Kuvyrkov
2024-01-11 17:51 ` Frank Ch. Eigler
2024-01-16 10:28 ` Maxim Kuvyrkov
2024-01-16 16:15 ` Frank Ch. Eigler
2024-01-16 16:49 ` Christophe Lyon
2024-01-16 17:10 ` Frank Ch. Eigler [this message]
2024-04-15 15:06 ` Frank Ch. Eigler
2024-04-18 14:44 ` Christophe Lyon
2024-04-18 14:50 ` Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240116171017.GH26700@redhat.com \
--to=fche@redhat.com \
--cc=bunsen@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=maxim.kuvyrkov@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).