Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>
Subject: [PUSHED 0/2] Make local-remote-host.exp force pseudo-tty allocation; add local-remote-host-notty.exp
Date: Thu, 01 May 2014 16:27:00 -0000	[thread overview]
Message-ID: <1398961655-7899-1-git-send-email-palves@redhat.com> (raw)
In-Reply-To: <1395812833-17748-1-git-send-email-yao@codesourcery.com>

On 03/26/2014 05:47 AM, Yao Qi wrote:
> The completion feature and other features on readline depend on the
> readline library.  However, readline library is not always used, for
> example, running testsuite like
> 
>   make check RUNTESTFLAGS="--host_board=local-remote-host"
> 
> the input stream is not a tty, and GDB doesn't use readline library
> as a result.

It's kind of lame that the board does that though.  There are testing
setups that can't do better, so it's good to be able to good emulate
them, but unix-like setups can just use "ssh -t" when spawning
interactive programs.

I pushed the series below.  With:

 make check RUNTESTFLAGS="--host_board=local-remote-host" \
      TESTS="gdb.ada/complete.exp \
      gdb.base/filesym.exp \
      gdb.base/macscp.exp \
      gdb.base/readline-ask.exp \
      gdb.base/readline.exp \
      gdb.python/py-cmd.exp \
      gdb.trace/tfile.exp"

(the tests you touched) we still get:

 $ cat testsuite/gdb.sum| grep "^FAIL"
 FAIL: gdb.trace/tfile.exp: target tfile tfile-basic.tf
 FAIL: gdb.trace/tfile.exp: info tracepoints on trace file
 FAIL: gdb.trace/tfile.exp: tfind 0 on trace file
 FAIL: gdb.trace/tfile.exp: print nonconstglob on trace file
 FAIL: gdb.trace/tfile.exp: tstatus on trace file
 FAIL: gdb.trace/tfile.exp: target tfile tfile-error.tf
 FAIL: gdb.trace/tfile.exp: tstatus on error trace file
 FAIL: gdb.trace/tfile.exp: interpreter-exec mi "-target-select tfile tfile-basic.tf"
 FAIL: gdb.trace/tfile.exp: -trace-status
 FAIL: gdb.trace/tfile.exp: complete-command 'target tfile'
 FAIL: gdb.base/readline-ask.exp: ask message (timeout)
 FAIL: gdb.ada/complete.exp: compilation foo.adb

though that looks like forward progress anyhow.  The tfile.exp issue
looks like completely unrelated.

Pedro Alves (2):
  Rename testsuite/boards/local-remote-host.exp ->
    testsuite/boards/local-remote-host-notty.exp
  New testsuite/boards/local-remote-host.exp board, now with editing
    on

 gdb/testsuite/ChangeLog                          |  9 +++++
 gdb/testsuite/boards/local-remote-host-notty.exp | 46 ++++++++++++++++++++++++
 gdb/testsuite/boards/local-remote-host.exp       | 38 +++++++-------------
 3 files changed, 67 insertions(+), 26 deletions(-)
 create mode 100644 gdb/testsuite/boards/local-remote-host-notty.exp

-- 
1.7.11.7


  parent reply	other threads:[~2014-05-01 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  5:49 [PATCH] Skip tests on completion and readline when readline lib isn't used Yao Qi
2014-03-26 12:32 ` Joel Brobecker
2014-03-26 13:13   ` Yao Qi
2014-05-01 16:27 ` Pedro Alves [this message]
2014-05-01 16:27   ` [PUSHED 1/2] Rename testsuite/boards/local-remote-host.exp -> testsuite/boards/local-remote-host-notty.exp Pedro Alves
2014-05-01 16:27   ` [PUSHED 2/2] New testsuite/boards/local-remote-host.exp board, now with editing on Pedro Alves
2014-05-02 11:28     ` Yao Qi

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=1398961655-7899-1-git-send-email-palves@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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