From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>,
buildbot@sourceware.org, bunsen@sourceware.org
Subject: Re: easier buildbot -> bunsen linkage
Date: Thu, 17 Aug 2023 16:08:59 +0200 [thread overview]
Message-ID: <1820e8f0a7871a8889c41600177ade183b0bca79.camel@klomp.org> (raw)
In-Reply-To: <20230816232314.GA22202@redhat.com>
On Wed, 2023-08-16 at 19:23 -0400, Frank Ch. Eigler wrote:
> Over time, the links may break, as the bunsen database is regularly
> aged. But for the most recent 100,000 or so builds, this should give
> an easier way to hop right into the analysis system. Enjoy!
For context, there are ~15,000 builds a month, but not all upload
results to bunsen. So getting at 100,000 builds (with bunsen results)
should take 6 till 12 months.
prev parent reply other threads:[~2023-08-17 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 23:23 Frank Ch. Eigler
2023-08-17 14:08 ` Mark Wielaard [this message]
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=1820e8f0a7871a8889c41600177ade183b0bca79.camel@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=bunsen@sourceware.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).