From: "Jose E. Marchesi" <jemarch@gnu.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: "Arsen Arsenović via poke-devel" <poke-devel@gnu.org>,
buildbot@sourceware.org, positron@gnu.org
Subject: Re: [PATCH builder.git] master.cfg: add GNU poke builder
Date: Sun, 20 Nov 2022 15:12:24 +0100 [thread overview]
Message-ID: <8735adaf5j.fsf@gnu.org> (raw)
In-Reply-To: <86edtxvlbn.fsf@aarsen.me> ("Arsen =?utf-8?Q?Arsenovi=C4=87?= =?utf-8?Q?=22's?= message of "Sun, 20 Nov 2022 13:21:31 +0100")
> Hi,
>
> "Jose E. Marchesi" <jemarch@gnu.org> writes:
>
>> Hi Arsen.
>> Thank you so much for working on this.
>
> Happy to help! :)
>
>> Regarding CPUs, Jitter is quite sensible to them when run in
>> non-threaded mode, so it is a good thing to test on them in order to
>> detect issues before releases.
>>
>> For example, we had several problems with (if I remember properly) arm
>> 32-bit and some other arch with poke 2.0.
>>
>> Mohammad and Luca may have particular suggestions..
>
> Sure, let's wait for them to chime in.
Actually, would it be to abuse much to just run the tests in all
supported architectures in the buildbot? I don't think there is any
architecture there that we do _not_ want to support...
next prev parent reply other threads:[~2022-11-20 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 23:36 Arsen Arsenović
2022-11-20 11:48 ` Jose E. Marchesi
2022-11-20 12:21 ` Arsen Arsenović
2022-11-20 13:17 ` Frank Ch. Eigler
2022-11-20 14:43 ` Arsen Arsenović
2022-11-20 15:31 ` Frank Ch. Eigler
2022-11-20 16:05 ` Arsen Arsenović
2022-11-20 14:12 ` Jose E. Marchesi [this message]
2022-11-23 0:37 ` Mark Wielaard
2022-11-23 11:53 ` Jose E. Marchesi
2022-11-23 17:44 ` Mark Wielaard
2022-11-23 20:20 ` Mohammad-Reza Nabipoor
2022-11-24 12:11 ` Mark Wielaard
2022-11-28 16:48 ` Frank Ch. Eigler
2022-11-28 19:09 ` Arsen Arsenović
2022-11-28 21:53 ` Frank Ch. Eigler
2022-11-29 11:55 ` Mohammad-Reza Nabipoor
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=8735adaf5j.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=arsen@aarsen.me \
--cc=buildbot@sourceware.org \
--cc=poke-devel@gnu.org \
--cc=positron@gnu.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).