From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: alankao@andestech.com
Subject: Re: Cross-compiling test flow for libc-test
Date: Thu, 31 Oct 2019 12:32:38 +0100 [thread overview]
Message-ID: <20191031113237.GC4396@port70.net> (raw)
In-Reply-To: <20191031060405.GA22068@APC301.andestech.com>
* Ruinland ChuanTzu Tsai <ruinland@andestech.com> [2019-10-31 14:04:06 +0800]:
> Hi,
> sorry for sending this email out of the blue.
>
> I'm wondering whether there are any (official) guides about how to do
> cross-compiling tests for libc-test ?
>
> If I understand the Makefile of libc-test correctly, it will compile
> test units and then execute those tests on _host_ platform right away.
>
> Somehow, whilst I was cross-testing glibc, there's a script,
> cross-test-ssh.sh, which could be used with `test-wrapper` hook to ex-
> ecute those freshly compiled test units on a hetero-architecture platf-
> orm via ssh connections.
>
> If there's no such mechanism for libc-test at this time being, then I'm
> willing to develope one.
i think you can override the RUN_TEST or RUN_WRAP make
variables in your config.mak to run things under qemu
or via ssh (you can introduce similar hook there in
the makefile if it's not enough)
>
> That being said, I'm curious about how's the attitude which maintainers
> take toward this kind of testing flow.
>
> Aside from cross-testing, I also wonder the status of testing reports
> for releases on currently supported CPU architectures.
> As I was running libc-test on x86_64, some of functional and regression
> tests fail.
>
> Is there a validating rule (e.g. funcional/xxx and regression/yyy must
> pass) for code checking-in which I can enforce locally before
> submitting patches here ?
yes libc test is not in a great shape, some of the
reported errors are real just not high priority,
i think currently you can run it on x86_64 and
compare the results you get on whatever other
platform to that.
next prev parent reply other threads:[~2019-10-31 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 6:04 Ruinland ChuanTzu Tsai
2019-10-31 11:32 ` Szabolcs Nagy [this message]
2019-10-31 13:19 ` 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=20191031113237.GC4396@port70.net \
--to=nsz@port70.net \
--cc=alankao@andestech.com \
--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).