From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 3326 invoked from network); 16 Dec 2021 11:40:21 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 16 Dec 2021 11:40:21 -0000 Received: (qmail 18001 invoked by uid 550); 16 Dec 2021 11:40:19 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 17967 invoked from network); 16 Dec 2021 11:40:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alpinelinux.org; s=smtp; t=1639654807; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6B1ulW1dSzwE65XyJNE8roH0Yeh8y4wiZ2fv9fB///Y=; b=wi7pt4v1cYKAzFJk4+dPZE9HeZ6BVEwdEN1EgGdsYUh963KyTckbgT7pQtCYzCmmGpsUie n3ZgJI7zqiHO+WF8+ZURp0FpmBzCGqtHp7dgTtNcseDtrj3b8Lh2vO+FAuUPBC0vplm6DE k5SsobUUteUB5ZE5FKgaclqUs8OBAVc= Date: Thu, 16 Dec 2021 12:40:05 +0100 From: Natanael Copa To: Rich Felker Cc: musl@lists.openwall.com Message-ID: <20211216120253.158cc852@ncopa-desktop.lan> In-Reply-To: <20211216050220.GL7074@brightrain.aerifal.cx> References: <8ed85057-5ad8-1341-ba02-46bb15ee04bd@dustri.org> <5faf9ff0eaa6b72ac3c3b22e3a41bde071ae5806.camel@zv.io> <20211216050220.GL7074@brightrain.aerifal.cx> X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.30; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [musl] Current state and future of musl development infrastructure On Thu, 16 Dec 2021 00:02:20 -0500 Rich Felker wrote: > On Wed, Dec 15, 2021 at 04:52:05PM -0600, Zach van Rijn wrote: > > On Wed, 2021-12-15 at 22:22 +0100, jvoisin wrote: > > > Hello everyone, ... > > As for CI. > > > > It would probably be helpful to be able to run libc-test and > > perhaps other applications on a number of real hardware platforms > > in some automated manner. > > Yes. Having this automated would be really nice. Even better if it > could be done not just for the official upstream repo but for proposed > patches/patchsets or third-party git branches (on some sort of > request). I think it would be helpful to have the tests bundled in musl git repository and in release tarballs. It is common practice for downstream packagers to run `make && make check`, to run unit tests to have some basic smoke testing (that does not require root permissions). Depending on some external test suite (libc-test) is suboptimal because they may not catch recent additions, and it may be difficult to keep track of what is expected to pass or fail. I think it would make sense to have both a lighter/faster integrated set of unit tests, that are bundled with musl itself and have a more extensive (external) integration tests that is run with the CI. > I'd really love if the CI were optimized to do incremental builds and > reuse artifacts as much as possible for rapid results, but doing that > right probably requires fixing missing dependency tracking in the > build. Just an idea for incremental builds: Do out-of-tree builds. let the CI store a tarball of the out-of-tree build in some key/value storage, using the commit hash as the id. Subsequent builds tries fetch the old heads community id from storage and extract it to the out-of-tree build location. It might also be a good idea to try get it work first and optimize afterwards :) -nc