Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro_alves@portugalmail.pt>
Cc: "'GDB Patches'" <gdb-patches@sourceware.org>
Subject: RE: skip __main
Date: Tue, 29 Jan 2008 16:20:00 -0000	[thread overview]
Message-ID: <001701c86292$3d1e43c0$b75acb40$@u-strasbg.fr> (raw)
In-Reply-To: <479F44B5.2000406@portugalmail.pt>

OK, you are right. It better to leave "main".

		=== gdb Summary ===
 
-# of expected passes		9704
-# of unexpected failures	326
+# of expected passes		9867
+# of unexpected failures	163
 # of expected failures		59
 # of known failures		21
 # of unresolved testcases	37

I was wondering: you get much less errors
than I do, do you have any special restrictions 
applied on your testsuite?

  The number of expected passes is also lower than
mine, maybe you didn't use 'cvs up -d' for  
a while in the testsuite directory?
This is my last result on CVS gdb
that I got using 
make check RUNTESTFLAGS='--ignore manythreads.exp'

		=== gdb Summary ===

# of expected passes		10619
# of unexpected failures	529
# of unexpected successes	1
# of expected failures		58
# of known failures		31
# of unresolved testcases	38
# of untested testcases		14
# of unsupported tests		34
With your patch and the same RUNTESTFLAGS,
I go down to:
# of expected passes            10787
# of unexpected failures        351
# of unexpected successes       1
# of expected failures          58
# of known failures             32
# of unresolved testcases       38
# of untested testcases         14
# of unsupported tests          34
So I also get 178 errors less!
  
This is really good!

Pierre



  reply	other threads:[~2008-01-29 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29  5:35 Pedro Alves
2008-01-29  8:50 ` Pierre Muller
2008-01-29 15:48   ` Pedro Alves
2008-01-29 16:20     ` Pierre Muller [this message]
2008-01-29 20:26       ` Pedro Alves

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='001701c86292$3d1e43c0$b75acb40$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    /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