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] Update expected _gdb_major/_gdb_minor in default.exp Date: Sun, 13 Oct 2019 13:44:00 -0000 [thread overview] Message-ID: <dfee856674428aa0137efc3051eac170955f9532@gdb-build> (raw) *** TEST RESULTS FOR COMMIT dfee856674428aa0137efc3051eac170955f9532 *** commit dfee856674428aa0137efc3051eac170955f9532 Author: Tom de Vries <tdevries@suse.de> AuthorDate: Mon Oct 7 12:50:04 2019 +0200 Commit: Tom de Vries <tdevries@suse.de> CommitDate: Mon Oct 7 12:50:04 2019 +0200 [gdb/testsuite] Update expected _gdb_major/_gdb_minor in default.exp Now that commit "225f296a023 Change gdb/version.in to 9.0.50.DATE-git (new version numbering scheme)" has changed the gdb version number, we see: ... FAIL: gdb.base/default.exp: show convenience ($_gdb_major = 8 not found) ... Fix this by updating the expected _gdb_major/_gdb_minor to 9.1. Tested on x86_64-linux. gdb/testsuite/ChangeLog: 2019-10-07 Tom de Vries <tdevries@suse.de> * gdb.base/default.exp: Expect _gdb_major/_gdb_minor to be 9.1. diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index e2c3351e67..c3fc339a19 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,7 @@ +2019-10-07 Tom de Vries <tdevries@suse.de> + + * gdb.base/default.exp: Expect _gdb_major/_gdb_minor to be 9.1. + 2019-10-07 Andrew Burgess <andrew.burgess@embecosm.com> * lib/gdb.exp (gdb_test_multiple): Add gdb_test_name mechanism. diff --git a/gdb/testsuite/gdb.base/default.exp b/gdb/testsuite/gdb.base/default.exp index 0325b8045d..cf009cdc77 100644 --- a/gdb/testsuite/gdb.base/default.exp +++ b/gdb/testsuite/gdb.base/default.exp @@ -604,8 +604,8 @@ set show_conv_list \ {$_cimag = <internal function _cimag>} \ {$_creal = <internal function _creal>} \ {$_isvoid = <internal function _isvoid>} \ - {$_gdb_major = 8} \ - {$_gdb_minor = 4} \ + {$_gdb_major = 9} \ + {$_gdb_minor = 1} \ {$_shell_exitsignal = void} \ {$_shell_exitcode = 0} \ }
next reply other threads:[~2019-10-13 13:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-13 13:44 gdb-buildbot [this message] 2019-10-13 13:44 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot 2019-10-13 15:11 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot 2019-10-13 16:00 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2019-10-18 19:10 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot 2019-10-18 19:29 ` Failures on Fedora-i686, " gdb-buildbot 2019-10-18 20:14 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2019-10-18 20:40 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-10-18 21:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2019-10-18 21:49 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2019-10-18 22:16 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2019-10-18 22:49 ` Failures on Fedora-x86_64-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=dfee856674428aa0137efc3051eac170955f9532@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: linkBe 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).