public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Remove references to gdb64 in the testsuite Date: Fri, 13 Oct 2017 03:20:00 -0000 [thread overview] Message-ID: <8aed1c0d04e6d0eb7d0790c4691665cffef573b7@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 8aed1c0d04e6d0eb7d0790c4691665cffef573b7 *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 8aed1c0d04e6d0eb7d0790c4691665cffef573b7 Remove references to gdb64 in the testsuite I'm not sure whether this gdb64 was ever a thing in the upstream repo, but it certainly doesn't exist nowadays. AFAICT, this came in with the original big merge with the HP tree: https://sourceware.org/ml/gdb-patches/1999-q2/msg00149.html gdb/testsuite/ChangeLog: 2017-10-12 Pedro Alves <palves@redhat.com> * gdb.base/attach.exp: Remove references to gdb64. * gdb.base/dbx.exp: Remove references to gdb64.
next reply other threads:[~2017-10-13 3:20 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-13 3:20 sergiodj+buildbot [this message] 2017-10-13 3:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-13 9:22 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-10-13 9:27 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-13 9:51 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-13 10:16 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-13 22:19 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-13 22:29 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-13 22:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-13 23:02 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-13 23:30 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-10-13 23:57 ` Failures on Fedora-i686, " sergiodj+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=8aed1c0d04e6d0eb7d0790c4691665cffef573b7@gdb-build \ --to=sergiodj+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).