public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Carlos O'Donell <carlos@redhat.com>
Cc: tuliom@ascii.art.br, adhemerval.zanella@linaro.org,
	libc-alpha@sourceware.org
Subject: Re: New math test failures on Fedora/33
Date: Thu, 14 Jan 2021 14:19:10 +0100	[thread overview]
Message-ID: <mwo8hru04x.fsf@tomate.loria.fr> (raw)
In-Reply-To: <8338bca0-9b10-6ad7-3b3a-aa44c0c14970@redhat.com> (message from Carlos O'Donell on Thu, 14 Jan 2021 07:59:37 -0500)

       Dear Carlos,

> DJ and I have been discussing this as a project for 2021.
> 
> More importantly I think we need to shift this to CI/CD and integrate it
> into patchwork. I want to see fails reported per-patch. Then glue the
> CI/CD into that using new infrastructure (runners + builbot try bot).
> 
> I continue to feel that we need confidence to integrate new patches and
> that confidence doesn't come from build bots, but comes from CI/CD during
> review for reviewers assistance. I still want to get to 100 patches reviewed
> in a day and I need automated help to get there.
> 
> I want to see a process where we get email back immediately into a patch
> thread (consider each patch thread like a PR) and it includes a try bot
> result.
> 
> Then (and this idea I attribute to Konrad Kleine from the Red Hat Platform
> Tools team) I want the reviewer to interact with the try bot by email with
> special commands e.g. @build build-many-glibcs, to kick off a single bmg
> run with the patch in the thread that is tied to the patchwork object.
> This way the reviewer is in charge of exactly which background additional
> task is required to be carried out by CI/CD and report back the results
> in the thread for public review.

this looks quite promising!

> > I am no sure if we are allowed to run buildbots on gcc compiler farm
> > infrastructure.
>
> AFAIK we are not.
 
I asked people in charge of the gcc compiler farm and they told me that
glibc buildbots are welcome on the farm (Tulio and Adhemerval were in cc).

Paul

  reply	other threads:[~2021-01-14 13:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 16:00 H.J. Lu
2021-01-11 16:28 ` Adhemerval Zanella
2021-01-11 18:37   ` H.J. Lu
2021-01-11 19:21     ` Adhemerval Zanella
2021-01-12  7:13       ` Paul Zimmermann
2021-01-12 17:29         ` Adhemerval Zanella
2021-01-12 17:39           ` Siddhesh Poyarekar
2021-01-12 19:14           ` Tulio Magno Quites Machado Filho
2021-01-13  6:34             ` Paul Zimmermann
2021-01-13 12:51               ` Adhemerval Zanella
2021-01-14 12:48                 ` Carlos O'Donell
2021-01-14 12:59             ` Carlos O'Donell
2021-01-14 13:19               ` Paul Zimmermann [this message]
2021-01-14 14:47                 ` Carlos O'Donell
2021-01-14 13:07 ` Carlos O'Donell
2021-01-18 14:22 Wilco Dijkstra
2021-01-18 14:36 ` Paul Zimmermann
2021-01-18 14:36 ` Andreas Schwab
2021-01-18 15:18   ` Paul Zimmermann
2021-01-18 17:03     ` Andreas Schwab
2021-01-18 15:20   ` Wilco Dijkstra
2021-01-18 15:30     ` Carlos O'Donell
2021-01-18 15:38       ` Andreas Schwab
2021-01-18 16:58 ` Florian Weimer
2021-01-19 15:59 ` Patrick McGehearty

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=mwo8hru04x.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=tuliom@ascii.art.br \
    /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).