From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Simon Marchi <simark@simark.ca>
Cc: Luis Machado <luis.machado@linaro.org>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Regressions getting more common
Date: Wed, 14 Oct 2020 15:03:04 -0400 [thread overview]
Message-ID: <87v9fcbpg7.fsf@paluero> (raw)
In-Reply-To: <d3e5bce3-42a0-71b3-b22a-c0f698dfd0e4@simark.ca> (Simon Marchi's message of "Wed, 14 Oct 2020 10:41:45 -0400")
On Wednesday, October 14 2020, Simon Marchi wrote:
> Then, we can look at having try jobs work again. I never really liked
> submitting try jobs through the buildbot command line tool, I always
> found there was to little feedback (did my upload work? what jobs did I
> initiate?). I would receive test results by email and would have a ahrd
> time figuring out which result was for which patch.
>
> One idea would be to re-use the now abandonned Gerrit instance for this.
> Those who have use Gerrit will probably agree that it integrates quite
> well with CI. After pushing your patch for review, you can ask the CI
> to test a given patch (often by setting a label on it). The CI posts a
> comment on the patch with a link to the build, so you can follow it if
> you want. Once it has ran, the CI posts comments on the patch to say
> that version N of the patch has this result, again with a link to the
> build.
There is another idea, which is simpler to implement, which is to make
the Buildbot monitor user branches with a special naming convention,
like user/sergiodj/try-foobar or some such. When a new branch showed
up, the Buildbot would then build it, test things, and then send the
results via email to the author of the commit (bonus points if it can
also send an email to the committer). One of the problems to be solved
(not particular to this solution, but to the Buildbot in general) is to
decide which upstream commit the Buildbot will compare the results
against. If you're considering running one/two builds per day, this
problem becomes easier to solve. I had a hard time solving it because I
was running builds for every commit, as you know.
This was next on my TODO list for the Buildbot (along with stop building
separate commits, and start grouping them), but I could not find the
time to implement it.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
next prev parent reply other threads:[~2020-10-14 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 17:05 Luis Machado
2020-10-14 1:13 ` Matt Rice
2020-10-14 14:46 ` Simon Marchi
2020-10-14 15:49 ` Matt Rice
2020-10-14 14:41 ` Simon Marchi
2020-10-14 15:50 ` Rainer Orth
2020-10-14 19:03 ` Sergio Durigan Junior [this message]
2020-10-15 12:55 ` Luis Machado
2020-10-16 0:29 ` Simon Marchi
2020-10-14 15:14 ` Kamil Rytarowski
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=87v9fcbpg7.fsf@paluero \
--to=sergiodj@sergiodj.net \
--cc=gdb@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=simark@simark.ca \
/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).