This is the mail archive of the mauve-discuss@sourceware.cygnus.com mailing list for the Mauve project. See the Mauve home page for more information.
Never mind! It's a gmakeism. Which leads me to my next comment. Sometimes, tests will fail because they don't compile. Should that be a reason to bail out of the framework? - Godmar Forwarded message: > From mauve-discuss-return-20-gback=cs.utah.edu@sourceware.cygnus.com Thu Dec 3 14:26:51 1998 > Mailing-List: contact mauve-discuss-help@sourceware.cygnus.com; run by ezmlm > Precedence: bulk > X-No-Archive: yes > Delivered-To: mailing list mauve-discuss@sourceware.cygnus.com > From: Godmar Back <gback@cs.utah.edu> > Message-Id: <199812032127.OAA26635@sal.cs.utah.edu> > Subject: Re: What are we testing ? > To: green@cygnus.com (Anthony Green) > Date: Thu, 3 Dec 1998 14:27:19 -0700 (MST) > Cc: gback@cs.utah.edu, tromey@cygnus.com, abies@pg.gda.pl, > mauve-discuss@sourceware.cygnus.com > In-Reply-To: <199812032113.NAA19732@hoser.cygnus.com> from "Anthony Green" at Dec 3, 98 01:13:14 pm > X-Mailer: ELM [version 2.4 PL25] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > > > > > > Godmar wrote: > > > Is Mauve at this point in a state where I can just check it out > > > and run it against a JVM? > > > > Yep. By default it runs agains Sun's JDK. > > > > hoser[1049] make KEYS=JDK1.1 check > > ok=no; \ > > if test -f .save-keys && test -f choices && test "`cat .save-keys`" = "JDK1.1"; then \ > > ok=yes; \ > > fi; \ > > here=`/bin/pwd`; \ > > if test "$ok" = no; then \ > > echo "JDK1.1" > .save-keys; \ > > cd ../m/mauve && /bin/sh choose $here JDK1.1; \ > > fi > > make check-local > > make[1]: Entering directory `/hoser/tuque/java/mb' > > ok=no; \ > > if test -f .save-keys && test -f choices && test "`cat .save-keys`" = "JDK1.1"; then \ > > ok=yes; \ > > fi; \ > > here=`/bin/pwd`; \ > > if test "$ok" = no; then \ > > echo "JDK1.1" > .save-keys; \ > > cd ../m/mauve && /bin/sh choose $here JDK1.1; \ > > fi > > cat classes | java gnu.testlet.SimpleTestHarness ../m/mauve > > FAIL: gnu.testlet.java.lang.Double.new_Double (number 1) > > FAIL: gnu.testlet.java.beans.DescriptorTest (number 1) > > FAIL: gnu.testlet.java.beans.IntrospectorTest (number 6) > > 3 of 491 tests failed > > make[1]: *** [check-local] Error 1 > > make[1]: Leaving directory `/hoser/tuque/java/mb' > > make: *** [check] Error 2 > > > > Hmmm, I see this: > > gback@marker [1485](/q/gback/mauve) > ./configure > creating cache ./config.cache > checking for a BSD compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... yes > checking for working aclocal... found > checking for working autoconf... found > checking for working automake... found > checking for working autoheader... found > checking for working makeinfo... found > checking whether to enable maintainer-specific portions of Makefiles... no > checking for a BSD compatible install... /usr/bin/install -c > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > updating cache ./config.cache > creating ./config.status > creating Makefile > gback@marker [1486](/q/gback/mauve) > make KEYS=JDK1.1 check > "Makefile", line 298: Could not find choices > make: fatal errors encountered -- cannot continue > >