From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16022 invoked by alias); 28 Jun 2018 20:35:56 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 16013 invoked by uid 89); 28 Jun 2018 20:35:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com From: DJ Delorie To: Florian Weimer Cc: libc-alpha@sourceware.org Subject: Re: RFC V3 [1/2] test-in-container In-Reply-To: (message from Florian Weimer on Tue, 26 Jun 2018 14:57:19 +0200) Date: Thu, 28 Jun 2018 20:35:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2018-06/txt/msg00921.txt.bz2 Florian Weimer writes: > I think we need something to run these tests outside the Makefile > framework, similar to testrun.sh. Mostly, you can do ./testrun.sh support/test-container ./some-program There's overhead in $srcdir/Rules to handle all the other environment variables needed for various tests, but you have that as a manual step the old way too. Otherwise, if you happen to be running a test with a container setup, it autodetects that. So this should work: $ ./testrun.sh support/test-container nss/tst-nss-test3 where it finds nss/tst-nss-test3/* and sets up the container for you.