public inbox for
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <>
To: "Jose E. Marchesi" <>
Cc: "Arsen Arsenović via poke-devel" <>,,
Subject: Re: [PATCH builder.git] master.cfg: add GNU poke builder
Date: Sun, 20 Nov 2022 13:21:31 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]


"Jose E. Marchesi" <> 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.

> As discussed in IRC, this is the script that Bruno uses in the gitlab
> CI.  I think replicating it may be good:

OK, looking at this, I think we could have:
- One builder that runs distcheck and saves the resulting tar(s), and
- N builders for each arch/distro combo we want to run on, that just run
  make check and save the result (like the patch already would).
  That *could* also involve multilib, though I think an i686 runner
  would be equivalent but less complicated?  Not sure.

That'd (AFAICT) replicate the behavior of current CI, save for optional
packages.  We could re-run configuration without those, too.

I think config.log should cover all the useful information config.status
and config.cache contains, so maybe we could also omit saving those?

Have a good day.
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2022-11-20 12:53 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ć [this message]
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
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:

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

  git send-email \ \ \ \ \ \ \

* 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).