From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118749 invoked by alias); 16 Mar 2019 16:36:52 -0000 Mailing-List: contact dwz-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: dwz-owner@sourceware.org Received: (qmail 118728 invoked by uid 89); 16 Mar 2019 16:36:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-24.8 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.1 spammy= X-Spam-Status: No, score=-24.8 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: mx1.suse.de X-Virus-Scanned: by amavisd-new at test-mx.suse.de Subject: Re: Added a buildbot for dwz To: Mark Wielaard Cc: dwz@sourceware.org References: <61673a59-1da8-2a7f-e15e-14ff05874a39@suse.de> <20190316163108.GA2435@wildebeest.org> From: Tom de Vries Message-ID: Date: Tue, 01 Jan 2019 00:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: <20190316163108.GA2435@wildebeest.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-SW-Source: 2019-q1/txt/msg00136.txt.bz2 On 16-03-19 17:31, Mark Wielaard wrote: > On Sat, Mar 16, 2019 at 04:23:25PM +0100, Tom de Vries wrote: >>> To celebrate that dwz now has a testsuite I added a buildbot: >>> https://builder.wildebeest.org/buildbot/#/builders?tags=dwz >>> >> >> I've just pushed a fix for a dejagnu warning on my laptop, and there I >> see no warnings anymore. >> >> However, all builds on the build bot that I checked show: >> ... >> WARNING: Couldn't find the global config file. >> ... >> >> I'm not sure if this should be fixed on the buildbot, or in the sources. > > Apparently this comes from not setting the DEJAGNU variable: > > There is an optional global site.exp, containing > configuration values that apply to DejaGnu > site-wide. runtest loads these values first. The global > site.exp contains the default values for all targets and > hosts supported by DejaGnu. This global file is identified > by setting the environment variable DEJAGNU to the name of > the file. If DEJAGNU is set, but the file cannot be > located, an error will be raised and runtest will abort. > > https://www.gnu.org/software/dejagnu/manual/Customizing-DejaGnu.html > > The following seems to always suppress the WARNING: > > diff --git a/Makefile b/Makefile > index 1aa208f..2a9898c 100644 > --- a/Makefile > +++ b/Makefile > @@ -26,9 +26,14 @@ hello: > dw2-restrict: > $(CC) $(TEST_SRC)/dw2-restrict.S -o $@ || touch $@ > > +# On some systems we need to set and export DEJAGNU to suppress > +# WARNING: Couldn't find the global config file. > +DEJAGNU ?= /dev/null > + > check: dwz $(TEST_EXECS) > mkdir -p testsuite-bin > cd testsuite-bin; ln -sf $(PWD)/dwz . > + export DEJAGNU=$(DEJAGNU); \ > export PATH=$(PWD)/testsuite-bin:$$PATH; export LC_ALL=C; \ > runtest --tool=dwz -srcdir testsuite $(RUNTESTFLAGS) > rm -Rf testsuite-bin $(TEST_EXECS) > > Does that make sense? Works for me. Thanks, - Tom