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: Tue, 16 Jan 2024 14:28:09 +0400 [thread overview]
Message-ID: <7AE27BD9-5332-496D-9A32-C49383A039B3@linaro.org> (raw)
In-Reply-To: <20240111175140.GI28684@redhat.com>
> On Jan 11, 2024, at 21:51, Frank Ch. Eigler <fche@redhat.com> wrote:
>
> 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
We can fix that.
>
> - 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
We partially re-run the testsuites when results change unexpectedly. This allows us to detect and ignore flaky tests. 00-sumfiles/ is an auxiliary directory that contains all run and re-run logs and .sum files; sumfiles/ directory contains the final [synthetic] .sum files that are a merge of all re-run .sum files. All this is to say that we don't necessarily have the matching logs for the final [synthetic] .sum files.
What information do you extract from the .log files?
>
> - for buildbot builds on sourceware, we collect & parse the autoconf
> config.log files as first class content, rather than just informal
> console logs
We can gather config.log files.
>
> - 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
>
Ack.
>
> 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.
>
These are also uploaded outside of git repos, but it's not a problem to push uncompressed files into git.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
next prev parent reply other threads:[~2024-01-16 10:28 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 [this message]
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=7AE27BD9-5332-496D-9A32-C49383A039B3@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).