public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Add PR number to KFAIL in gdb.opt/inline-cmds.exp
Date: Mon, 11 May 2020 01:55:01 -0400	[thread overview]
Message-ID: <56a4f5a10b1e90d60527455b8542ba98fd0f6349@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 56a4f5a10b1e90d60527455b8542ba98fd0f6349 ***

commit 56a4f5a10b1e90d60527455b8542ba98fd0f6349
Author:     Tom de Vries <tdevries@suse.de>
AuthorDate: Tue Apr 28 08:33:40 2020 +0200
Commit:     Tom de Vries <tdevries@suse.de>
CommitDate: Tue Apr 28 08:33:40 2020 +0200

    [gdb/testsuite] Add PR number to KFAIL in gdb.opt/inline-cmds.exp
    
    With test-case gdb.opt/inline-cmds.exp, we have:
    ...
    KFAIL: gdb.opt/inline-cmds.exp: next to second func1 (PRMS: gdb/NNNN)
    ...
    
    I've filed PR25884 for this failure.
    
    Set the KFAIL PR accordingly.
    
    gdb/testsuite/ChangeLog:
    
    2020-04-28  Tom de Vries  <tdevries@suse.de>
    
            * gdb.opt/inline-cmds.exp: Set KFAIL PR.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index b51ec118b1..2d26a5e90e 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2020-04-28  Tom de Vries  <tdevries@suse.de>
+
+	* gdb.opt/inline-cmds.exp: Set KFAIL PR.
+
 2020-04-28  Tom de Vries  <tdevries@suse.de>
 
 	* gdb.base/info-macros.exp: Remove KFAIL.  Add missing trailing ".*".
diff --git a/gdb/testsuite/gdb.opt/inline-cmds.exp b/gdb/testsuite/gdb.opt/inline-cmds.exp
index aa8c8c6bfa..94314fe2e4 100644
--- a/gdb/testsuite/gdb.opt/inline-cmds.exp
+++ b/gdb/testsuite/gdb.opt/inline-cmds.exp
@@ -235,7 +235,7 @@ gdb_test_multiple "next" $msg {
 	# containing block and/or function into account when
 	# deciding how far to step.  The single line table entry
 	# is actually two consecutive instances of the same line.
-	kfail gdb/NNNN $msg
+	kfail gdb/25884 $msg
     }
 }
 


             reply	other threads:[~2020-05-11  5:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11  5:55 gdb-buildbot [this message]
2020-05-11  5:55 ` Failures on Fedora-i686, branch master gdb-buildbot
2020-05-11  6:09 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-05-11  6:28 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-05-11  6:43 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-05-11  7:10 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-05-11  7:29 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-05-12 10:03 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-05-13 21:51 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2020-05-17 16:13 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot

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=56a4f5a10b1e90d60527455b8542ba98fd0f6349@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).