public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: buildbot@sourceware.org, bunsen@sourceware.org
Subject: easier buildbot -> bunsen linkage
Date: Wed, 16 Aug 2023 19:23:14 -0400	[thread overview]
Message-ID: <20230816232314.GA22202@redhat.com> (raw)

Hi -

With help from Mark and the gods of sqlite and python3, we now have
buildbot jobs provide a user-friendly link to the bunsen analysis for
each.  e.g.:

https://builder.sourceware.org/buildbot/#/builders/140/builds/172

Look at the "upload to bunsen" step.  There is now a link labeled
"bunsen", which points to the analyzed testrun data.

This information should be automatically present in all future builds,
and is being approximately retrofitted into many older builds (via
sqlite/shell-script hacking) as we speak.

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!

- FChE


             reply	other threads:[~2023-08-16 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 23:23 Frank Ch. Eigler [this message]
2023-08-17 14:08 ` Mark Wielaard

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=20230816232314.GA22202@redhat.com \
    --to=fche@redhat.com \
    --cc=buildbot@sourceware.org \
    --cc=bunsen@sourceware.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).