From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14891 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Ruinland ChuanTzu Tsai Newsgroups: gmane.linux.lib.musl.general Subject: Cross-compiling test flow for libc-test Date: Thu, 31 Oct 2019 14:04:06 +0800 Message-ID: <20191031060405.GA22068@APC301.andestech.com> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="216046"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.9.4 (2018-02-28) Cc: To: Original-X-From: musl-return-14907-gllmg-musl=m.gmane.org@lists.openwall.com Thu Oct 31 07:04:31 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1iQ3ZN-000u4q-Rx for gllmg-musl@m.gmane.org; Thu, 31 Oct 2019 07:04:29 +0100 Original-Received: (qmail 7456 invoked by uid 550); 31 Oct 2019 06:04:27 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 7414 invoked from network); 31 Oct 2019 06:04:25 -0000 Content-Disposition: inline X-Originating-IP: [10.0.12.139] X-MAIL: ATCSQR.andestech.com x9V5kNWQ030545 Xref: news.gmane.org gmane.linux.lib.musl.general:14891 Archived-At: 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. 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 ? Sincerely, Ruinland ChuanTzu Tsai