From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: exit status of 'make check'
Date: Sun, 11 Nov 2001 22:14:00 -0000 [thread overview]
Message-ID: <20011125015054.A31912@nevyn.them.org> (raw)
In-Reply-To: <01112208082500.16429@shadowfax.middleearth>
On Thu, Nov 22, 2001 at 08:08:25AM -0500, George France wrote:
> Hello Michael,
>
> It has been a while since we chatted. I hope you are doing well.
>
> > > When I ever I do a 'make check' on gdb using the cvs HEAD tree on either
> > > the intel or Alpha architecture. It always returnes a non-zero exit code.
> > > The testsuites execute and produce a good gdb.log and gdb.sum files. Has
> > > anybody seen this before??
> >
> > Yes, this is normal. I just do:
> >
> > make check || true
>
> This was not exactly the solution that I was hoping for. :-) We need to fix
> this problem. It would be really useful to know if 'make check' did or did
> not have an anomaly.
>
> Any Ideas before I go mucking about?
>
> Best Regards,
That pretty much means that it did. You can grep for ^FAIL: to see how
many there are. I'm hoping to see the GDB testsuite pass entirely for
some target, someday...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-25 6:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 10:33 Michael Elizabeth Chastain
2001-11-11 11:30 ` George France
2001-11-11 22:14 ` Daniel Jacobowitz [this message]
2001-11-12 15:02 ` George France
2001-11-13 8:47 ` Daniel Jacobowitz
2001-11-13 9:53 ` George France
2001-11-13 10:05 ` Daniel Jacobowitz
2001-11-13 10:26 ` George France
2001-11-25 20:59 ` George France
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 10:34 Michael Elizabeth Chastain
2001-11-13 12:38 ` George France
2001-11-25 22:21 ` George France
2001-11-25 21:11 ` Michael Elizabeth Chastain
2001-11-10 10:17 George France
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=20011125015054.A31912@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.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