mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] musl CI?
Date: Tue, 17 Nov 2020 10:52:42 -0500	[thread overview]
Message-ID: <20201117155241.GZ534@brightrain.aerifal.cx> (raw)
In-Reply-To: <20201117065212.GA12665@APC301.andestech.com>

On Tue, Nov 17, 2020 at 02:52:13PM +0800, Ruinland ChuanTzu Tsai wrote:
> Hi all,
> 
> Glad to know there are discussions about CI.
> Sorry that I couldn't find the IRC log and thus I might be saying some-
> thing which had already been disccussed.
> 
> Though might be irrevalent, I'm wondering which platforms are the
> "golden standard" for such CI to run against for each musl supported
> architecture ?
> 
> My rough hunch is something like : latest LTS Linux kernel
> (which is 5.4 for now) running on QEMU "virt machine" with full-system
> emulation or qemu-user ?

This is a really good question. I might lean towards newer (latest
stable) and older to catch breakage from use of newly added syscalls
or broken fallback on much older kernels.

> The reason why I prefer running testsuite under a fully-emulated Linux
> instead of qemu-user is that I don't have too much faith on its syscall
> -translation and signal-handling mechanism to work out perfectly when
> the guest and host architecture are heterogeneous.
> (This is just my prejudice, please correct me if I worry too much.)

Same. qemu-user is not really good as anything beyond a smoke test; it
has too many false positives and negatives from broken emulation.

Rich

  reply	other threads:[~2020-11-17 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  4:09 Rich Felker
2020-11-17  6:52 ` Ruinland ChuanTzu Tsai
2020-11-17 15:52   ` Rich Felker [this message]
2020-11-17  8:39 ` Ruinland ChuanTzu Tsai
2020-11-17  9:44   ` Arnd Bergmann
2020-11-17 12:04 ` Leah Neukirchen
2020-11-17 15:48   ` Rich Felker

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=20201117155241.GZ534@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).