From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5703 Path: news.gmane.org!not-for-mail From: Bobby Bingham Newsgroups: gmane.linux.lib.musl.general Subject: Re: Building a solid musl automated-testing framework Date: Mon, 4 Aug 2014 00:10:12 -0500 Message-ID: <20140804051012.GA8714@duality.lan> References: <20140731214716.GA27647@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" X-Trace: ger.gmane.org 1407129282 7844 80.91.229.3 (4 Aug 2014 05:14:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Aug 2014 05:14:42 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5708-gllmg-musl=m.gmane.org@lists.openwall.com Mon Aug 04 07:14:37 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XEAbT-0003fT-DB for gllmg-musl@plane.gmane.org; Mon, 04 Aug 2014 07:14:35 +0200 Original-Received: (qmail 7899 invoked by uid 550); 4 Aug 2014 05:14:33 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7886 invoked from network); 4 Aug 2014 05:14:33 -0000 Content-Disposition: inline In-Reply-To: <20140731214716.GA27647@brightrain.aerifal.cx> X-Operating-System: Linux duality 3.13.5-gentoo User-Agent: Mutt/1.5.22 (2013-10-16) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Xref: news.gmane.org gmane.linux.lib.musl.general:5703 Archived-At: --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Thu, Jul 31, 2014 at 05:47:16PM -0400, Rich Felker wrote: > I'd like to figure out how to setup the openadk test framework, or > adapt things from it, for automated testing all musl ports. The repo I like this idea. I'll probably start looking into putting this together soon if nobody gets to it first. > is here: > > http://www.openadk.org/cgi-bin/gitweb.cgi?p=adk-test-framework.git > > There's a lot of stuff hard-coded for the openadk toolchains, whereas > I'd like to be able to use it with the musl-cross toolchains which are > more canonical. The scripts also seem to be incompatible with busybox > (using GNU features in something for making the initramfs, probably > cpio?). And by default it tries to test musl 1.0.1 and doesn't have an > obvious way to test from git. > > The idea I have in mind for using it as a basis for automated testing > would be: > > 1. Have a Makefile and a subdirectory full of cross compiler trees. > The set of archs could be based purely on the set of cross > compilers, computed by the Makefile based on directory contents. > > 2. Have the Makefile clone/pull one musl tree from upstream git and > then clone/pull an additional copy of the tree per arch/subarch > (with the set of archs determined as in point 1). > > 3. Build each musl (via recursive make, i.e. make calling configure > and make in each musl clone) and install them into the cross > compiler include/lib dirs for their corresponding cross compilers. > > 4. Do like points 2 and 3, but for libc-test repo. > > 5. Use the kernel, initrd, and qemu stuff from the adk-test-framework > to build initrd images and run them. > Last I looked, libc-test didn't support being built on one system and run on another. Has this changed? > The idea of using a Makefile (aside from declarative being The Right > Way to do anything like this :) is to make it easy to make a single > fix and re-run the test without rebuilding everything. Of course +1 > rebuilding (via a "make clean" or similar) should aof coursebe an > option and what's usually used. > > Does any of this make sense? Or is it simpler to get this kind of > automated testing just making a few tweaks to the existing scripts? > > It would be ideal if the whole thing would work with dumping the test > repo on a system not necessarily setup for running it (e.g. some kind > of build farm or 'cloud computing' resource) and just produce the > results that could be read offline. +1 > > Rich -- Bobby Bingham --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJT3xW0AAoJEFedFv6RmqC976AP/Rwr2l9iz4F5EQvpY4OYXNi1 i3geA5+AmRFJxdCkODIp7nbmK0CepA7aFyGJzUsMQ49NxjPi+OnVqPz+0zGqakoJ fLDNSgfoP3XxEt/6LmNTJgvOagIPy5yETTDMVUaVswLTUxJ1PxxVT1O82QPGTdIk TWmK8wRNIukdlzHw6bKzfsffHvjWKF445WdTOL+0a+BLNTTL4ea46p5M66x7MmJq sP+v/LjRprOqfVK1exc2zuy0TScmn/zoiw+sWtDqNSO43KJ5DoWBEu69N5Sb/8Cb n/K8GYY3etwWdgl7PhodDXKre6pJ2+m4SEizAPaGEYAZdcewpdibWnJB3cvVOHuH owdlCsRopz/Xr1qZ1O4gEjP7m7JET48yJ9LqVYwacToinPDl/iHYymwGwIVg3qOU 2F4Di/Wx/5iOrbS4sND+DJsKpzpvMJr3KmGRN+PI8WjcS/nFugP8sNdpL1oF6BhI MtEKtN2qFojEL/rCadCe5QTlnEayQiqkPAiE/yheaOYfBTzFxntshVncS4t0DR9E KLE/xgTdmhkfoT4GYFxckz4/LUo/ts7Pgd0L5rBMPL+xwhfJvNgDabF8iiQfJLMe FvU9Xy+/IrlP+KcCmtKT8MrNog37d0MZijd8qyHqVYXytoe4NgByYDmpGZ4prIyx 9KOXlNQUlR8ZvJycKnMM =v/oH -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--