From: "Frank Ch. Eigler" <fche@redhat.com>
To: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: bunsen@sourceware.org, Christophe Lyon <christophe.lyon@linaro.org>
Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs
Date: Wed, 3 Jan 2024 21:34:00 -0500 [thread overview]
Message-ID: <20240104023400.GA17157@redhat.com> (raw)
In-Reply-To: <C9C9D457-C797-428F-AD6E-C8009FD320A7@linaro.org>
Hi -
> This approach matches well with our CI system. We already store results in a git repo, and post-process them for publishing to LNT dashboard (e.g., [1]).
OK, will check that out. Is the git repo with results also visible somewhere?
> Re. ssh access -- could you create an account for linaro-tcwg-bot with ssh key [2]?
Done. For namespace disambiguation, you're welcome to use a tag
prefix such as "linaro-tcwg/" and push bunsen style commits with log
files & .bunsen metadata into ssh://sourceware.org/git/bunsendb.git .
You can of course download the current repo to see the style of
testsuite runs, so you can match that as much as practical.
> [1] http://llvm.validation.linaro.org:38000/db_default/v4/tcwg_gdb_check/graph?plot.14.0=1.14.0&plot.11.2=1.11.2
Neat.
- FChE
next prev parent reply other threads:[~2024-01-04 2:34 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 [this message]
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=20240104023400.GA17157@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).