From: "Frank Ch. Eigler" <fche@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: bunsen@sourceware.org
Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs
Date: Mon, 15 Apr 2024 11:06:22 -0400 [thread overview]
Message-ID: <20240415150622.GB24230@redhat.com> (raw)
In-Reply-To: <20240116171017.GH26700@redhat.com>
Hi -
Have y'all had time to try to start feeding some of your ci/cd logs into
sourceware's bunsen repo? Is there any obstacle at all from our side?
- FChE
next prev parent reply other threads:[~2024-04-15 15:06 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
2024-04-15 15:06 ` Frank Ch. Eigler [this message]
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=20240415150622.GB24230@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).