From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14892 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Cross-compiling test flow for libc-test Date: Thu, 31 Oct 2019 12:32:38 +0100 Message-ID: <20191031113237.GC4396@port70.net> References: <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="238091"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.10.1 (2018-07-13) Cc: alankao@andestech.com To: musl@lists.openwall.com Original-X-From: musl-return-14908-gllmg-musl=m.gmane.org@lists.openwall.com Thu Oct 31 12:32:52 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 1iQ8hA-000zoX-SB for gllmg-musl@m.gmane.org; Thu, 31 Oct 2019 12:32:52 +0100 Original-Received: (qmail 5820 invoked by uid 550); 31 Oct 2019 11:32:50 -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 5802 invoked from network); 31 Oct 2019 11:32:49 -0000 Mail-Followup-To: musl@lists.openwall.com, alankao@andestech.com Content-Disposition: inline In-Reply-To: <20191031060405.GA22068@APC301.andestech.com> Xref: news.gmane.org gmane.linux.lib.musl.general:14892 Archived-At: * Ruinland ChuanTzu Tsai [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.