From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: bunsen@sourceware.org, Christophe Lyon <christophe.lyon@linaro.org>
Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs
Date: Thu, 14 Dec 2023 18:45:02 +0300 [thread overview]
Message-ID: <86711582-4DD8-46F4-824C-583CB19EA58D@linaro.org> (raw)
In-Reply-To: <20231212185006.GA21248@redhat.com>
> On Dec 12, 2023, at 21:50, Frank Ch. Eigler <fche@redhat.com> wrote:
>
> Hi -
>
> I write to investigate any possible linkage between your work at
> linaro betweween the toolchain ci/cd work and our work with upstream
> testing on sourceware. Part of it is via buildbot, that I'm sure you
> know; testsuite log archiving/analysis is done with a gadget called
> bunsen. I believe you met Mark Wielaard over at Cauldron and talked
> briefly about this stuff. Is there any material or time I could offer
> to explain what we have, so as to investigate any opportunities to
> interoperate?
>
> https://sourceware.org/bunsen/
Hi Frank,
How about a zoom/hangout/etc. call next week? [Christophe and I are in Europe timezone.]
One obvious opportunity is to make Linaro Toolchain CI submit results to bunsen. Are there other things we can improve?
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
next prev parent reply other threads:[~2023-12-14 15:45 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 [this message]
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
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=86711582-4DD8-46F4-824C-583CB19EA58D@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=bunsen@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=fche@redhat.com \
/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).