From: Joel Brobecker <brobecker@adacore.com>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING] [PATCH] Fix gdb.fortran/array-element.exp failures.
Date: Tue, 09 Sep 2014 15:45:00 -0000 [thread overview]
Message-ID: <20140909154531.GJ28404@adacore.com> (raw)
In-Reply-To: <87d2b4c07h.fsf@anubis.Home>
> Sorry I didn't resend the original message with my pings. Here it goes.
>
> This fixes two FAIL results when running this test file due to a
> misplaced "continue" command, which caused the inferior to end execution
> prematurely.
>
> On trunk, we have:
>
> FAIL: gdb.fortran/array-element.exp: continue to breakpoint once again
> (the program exited)
> FAIL: gdb.fortran/array-element.exp: print the second element of array a
>
> === gdb Summary ===
>
> # of expected passes 3
> # of unexpected failures 2
>
> And now, we get:
> === gdb Summary ===
> # of expected passes 3
>
> Is this ok?
The problem is that this does not tell me what was wrong. Just that
some tests did not pass. Although your change seems OK at first glance,
I'd like to do know what it was that did not match, and why it's OK
stop trying to match it now.
--
Joel
next prev parent reply other threads:[~2014-09-09 15:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 5:58 Gabriel Krisman Bertazi
2014-07-04 15:35 ` Sergio Durigan Junior
2014-07-04 23:20 ` Gabriel Krisman Bertazi
2014-07-05 12:14 ` Sergio Durigan Junior
2014-07-05 17:17 ` Gabriel Krisman Bertazi
2014-07-06 19:03 ` Sergio Durigan Junior
2014-07-14 23:28 ` Gabriel Krisman Bertazi
2014-08-17 4:07 ` Gabriel Krisman Bertazi
2014-08-26 0:30 ` [PING] " Gabriel Krisman Bertazi
2014-09-04 19:31 ` Gabriel Krisman Bertazi
2014-09-09 13:09 ` Joel Brobecker
2014-09-09 14:55 ` Gabriel Krisman Bertazi
2014-09-09 15:45 ` Joel Brobecker [this message]
2014-09-09 18:17 ` Gabriel Krisman Bertazi
2014-09-10 12:50 ` Joel Brobecker
2014-09-10 16:11 ` Sergio Durigan Junior
2014-09-11 3:25 ` Gabriel Krisman Bertazi
2014-09-09 15:08 ` Sergio Durigan Junior
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=20140909154531.GJ28404@adacore.com \
--to=brobecker@adacore.com \
--cc=gabriel@krisman.be \
--cc=gdb-patches@sourceware.org \
/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