public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 11 Jan 2024 12:51:40 -0500	[thread overview]
Message-ID: <20240111175140.GI28684@redhat.com> (raw)
In-Reply-To: <C0B80CEB-D980-4C99-A761-D5634E23373D@linaro.org>

Hi -

> > OK, will check that out.  Is the git repo with results also visible somewhere?
> [...]
> [2] https://git.linaro.org/toolchain/ci/base-artifacts/tcwg_gcc_check/master-aarch64.git/

Just for reference, after a quick glance at this, it's close to but
not quite verbatim usable by bunsen:

- the .xz compression/extension would interfere with extension based
  matching

- separating the .log and .sum files into different directories stops
  bunsen's crossmatching of the two; bunsen can accept the build tree
  raw locations of these files, without the "sumfiles" / "00-sumfiles"
  type of reorg

- for buildbot builds on sourceware, we collect & parse the autoconf
  config.log files as first class content, rather than just informal
  console logs

- bunsen would love to receive metadata about the build in little
  .bunsen.FOO text files, e.g. see:
  https://sourceware.org/git/?p=bunsendb.git;a=commit;h=613dd3b381b0910ebd5036fcf42761e2cead12ee


I assume you had good reasons for .xz compressing these files inside
the git repo ... but for what it's worth, we find that letting normal
git-repack transparently manage all the compression of plain text
payloads gives us excellent results.


- FChE


  reply	other threads:[~2024-01-11 17:51 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 [this message]
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=20240111175140.GI28684@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).