unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
	libc-alpha@sourceware.org
Subject: Re: New math test failures on Fedora/33
Date: Tue, 12 Jan 2021 14:29:03 -0300	[thread overview]
Message-ID: <6eead3d5-56c7-1332-a978-8663bd296522@linaro.org> (raw)
In-Reply-To: <mwh7nmr5jw.fsf@tomate.loria.fr>



On 12/01/2021 04:13, Paul Zimmermann wrote:
>        Hi,
> 
> about such failures that come out several days after the corresponding commit,
> I'm surprised there is no continuous integration scheme with glibc. This would
> help to detect very soon such issues.
> 
> Paul
> 

We had buildbots setup for x86/i686 some time ago [1], but if I recall correctly
they were setup by Roland McGrath when he was a maintainer using the google
infrastructure. Since he left the project I am not sure the state of the bots.

Currently we only have aarch64/armhf that provide any meaningful information.
Maybe Tulio can give us a better idea of the current status of the powerpc
ones.

Afaik the infra of the waterfall server itself was done by Siddhesh.

I personally thing to have a working CI for at least the most usual architectures
would be a great thing, however I think we are lacking resources here.

[1] http://glibc-buildbot.reserved-bit.com/waterfall

  reply	other threads:[~2021-01-12 17:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 16:00 New math test failures on Fedora/33 H.J. Lu via Libc-alpha
2021-01-11 16:28 ` Adhemerval Zanella via Libc-alpha
2021-01-11 18:37   ` H.J. Lu via Libc-alpha
2021-01-11 19:21     ` Adhemerval Zanella via Libc-alpha
2021-01-12  7:13       ` Paul Zimmermann
2021-01-12 17:29         ` Adhemerval Zanella via Libc-alpha [this message]
2021-01-12 17:39           ` Siddhesh Poyarekar
2021-01-12 19:14           ` Tulio Magno Quites Machado Filho via Libc-alpha
2021-01-13  6:34             ` Paul Zimmermann
2021-01-13 12:51               ` Adhemerval Zanella via Libc-alpha
2021-01-14 12:48                 ` Carlos O'Donell via Libc-alpha
2021-01-14 12:59             ` Carlos O'Donell via Libc-alpha
2021-01-14 13:19               ` Paul Zimmermann
2021-01-14 14:47                 ` Carlos O'Donell via Libc-alpha
2021-01-14 13:07 ` Carlos O'Donell via Libc-alpha
  -- strict thread matches above, loose matches on Subject: below --
2021-01-18 14:22 Wilco Dijkstra via Libc-alpha
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 via Libc-alpha
2021-01-18 15:30     ` Carlos O'Donell via Libc-alpha
2021-01-18 15:38       ` Andreas Schwab
2021-01-18 16:58 ` Florian Weimer via Libc-alpha
2021-01-19 15:59 ` Patrick McGehearty via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6eead3d5-56c7-1332-a978-8663bd296522@linaro.org \
    --to=libc-alpha@sourceware.org \
    --cc=Paul.Zimmermann@inria.fr \
    --cc=adhemerval.zanella@linaro.org \
    --cc=tuliom@linux.vnet.ibm.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).