From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>,
Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
Cc: libc-alpha@sourceware.org
Subject: Re: New math test failures on Fedora/33
Date: Wed, 13 Jan 2021 09:51:54 -0300 [thread overview]
Message-ID: <62b06bef-34b0-acd4-af3a-dc0dc7b40f45@linaro.org> (raw)
In-Reply-To: <mwsg75mjkl.fsf@tomate.loria.fr>
I am no sure if we are allowed to run buildbots on gcc compiler farm
infrastructure.
On 13/01/2021 03:34, Paul Zimmermann wrote:
> Dear Tulio,
>
> are you using the GCC compile farm (https://cfarm.tetaneutral.net/)?
>
> Best regards,
> Paul
>
>> From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
>> Date: Tue, 12 Jan 2021 16:14:02 -0300
>>
>> Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org> writes:
>>
>>> 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.
>>
>> I lost access to the 3 servers I had a while ago.
>> It's been difficult to find 32-bit powerpc servers after that.
>>
>> During the pandemic, I also lost access to the ansible playbooks I used to
>> create the controller and the ppc workers.
>> I've just recovered them, but I'm able to add just ppc64le and ppc64 servers.
>> Not optimal, but better than what we have now.
>>
>> During the last 2 Cauldrons, we've also discussed improvements that are
>> necessary to make this BuildBot useful.
>> They're all still pending.
>>
>> In case there is anyone willing to help, the repository is available at:
>> https://sourceware.org/git/?p=glibc-buildbot.git;a=summary
>>
>> --
>> Tulio Magno
next prev parent reply other threads:[~2021-01-13 12:51 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 [this message]
2021-01-14 12:48 ` Carlos O'Donell
2021-01-14 12:59 ` Carlos O'Donell
2021-01-14 13:19 ` Paul Zimmermann
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=62b06bef-34b0-acd4-af3a-dc0dc7b40f45@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Paul.Zimmermann@inria.fr \
--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).