From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: -file-list-exec-source-files testsuite question
Date: Thu, 03 Jun 2004 14:38:00 -0000 [thread overview]
Message-ID: <20040603143824.GA4902@white> (raw)
Hi,
Before committing my -file-list-exec-source-files patch I am running the
testsuite a final time.
With a fresh checkout I get,
# of expected passes 10072
# of unexpected failures 32
# of unexpected successes 1
# of expected failures 52
# of unknown successes 40
# of known failures 73
# of unresolved testcases 1
# of untested testcases 3
# of unsupported tests 6
With my patch I get,
# of expected passes 10075
# of unexpected failures 31
# of unexpected successes 1
# of expected failures 52
# of unknown successes 40
# of known failures 73
# of unresolved testcases 2
# of untested testcases 3
# of unsupported tests 8
The number of expected passes makes sense to me, since I added some
results. I am concerned about the number of unsupported tests and the
number of unresolved testcases. What does this mean? Is this normal?
Finally, it looks like 1 unexpected failure was fixed. How can I find
more info about these?
Thanks,
Bob Rossi
next reply other threads:[~2004-06-03 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 14:38 Bob Rossi [this message]
2004-06-03 17:53 Michael Elizabeth Chastain
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=20040603143824.GA4902@white \
--to=bob@brasko.net \
--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