kfail two tests in no-unwaited-for-left.exp for remote target
authorYao Qi <yao.qi@linaro.org>
Thu, 2 Apr 2015 12:51:31 +0000 (13:51 +0100)
committerYao Qi <yao.qi@linaro.org>
Thu, 2 Apr 2015 12:51:31 +0000 (13:51 +0100)
commitcafda5977a98aef514ff86daca2fa94205bdd34e
treee0bc71059e61cfc3b6a074a67c6dc59bb48e113c
parent39f3de7c43926181f8f2f57bfa17d4fe9e5748a0
kfail two tests in no-unwaited-for-left.exp for remote target

I see these two fails in no-unwaited-for-left.exp in remote testing
for aarch64-linux target.

...
continue
Continuing.
warning: Remote failure reply: E.No unwaited-for children left.

[Thread 1084] #2 stopped.
(gdb) FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when thread 2 exits

....
continue
Continuing.
warning: Remote failure reply: E.No unwaited-for children left.

[Thread 1081] #1 stopped.
(gdb) FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits

I checked the gdb.log on buildbot, and find that these two fails also
appear on Debian-i686-native-extended-gdbserver and Fedora-ppc64be-native-gdbserver-m64.
I recall that they are about local/remote parity, and related RSP is missing.
There has been already a PR 14618 about it.  This patch is to kfail them
on remote target.

gdb/testsuite:

2015-04-02  Yao Qi  <yao.qi@linaro.org>

* gdb.threads/no-unwaited-for-left.exp: Set up kfail if target
is remote.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/no-unwaited-for-left.exp