public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Brian Jones <cbj@gnu.org>
Cc: mauve-discuss@sourceware.cygnus.com
Subject: Re: tests that pass but indicate an error?
Date: Thu, 21 Dec 2000 22:11:00 -0000	[thread overview]
Message-ID: <87ae9pdl88.fsf@creche.redhat.com> (raw)
In-Reply-To: <m3itodf1m7.fsf_-_@lyta.haphazard.org>

Brian> So I've executed mauve against japhar+classpath with a given key file
Brian> (that eliminates things that blow up) and one strange thing I've
Brian> noticed is a set of tests that indicate they "PASS" although the
Brian> -verbose message indicates "Error."  Examples included below.

Some of the Mauve tests were auto-converted from a different test
suite.  The messages weren't fully changed from failure notices to
checkpoint names.  Lame, I agree...

Tom

      reply	other threads:[~2000-12-21 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-20  3:08 Bytecode verifiers Bernard Serpette
2000-12-20  4:49 ` Peter Naulls
2000-12-20  9:51   ` Tom Tromey
2000-12-20 15:01     ` Peter Naulls
2000-12-21 21:48     ` tests that pass but indicate an error? Brian Jones
2000-12-21 22:11       ` Tom Tromey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ae9pdl88.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=cbj@gnu.org \
    --cc=mauve-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).