public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb] Allow multiple occurrences of the frames-invalid annotation in gdb.cp/annota2.exp Date: Fri, 27 Nov 2015 14:44:00 -0000 [thread overview] Message-ID: <88e8ec1b3e372dc1ea1cd0be44c59ca7760e9008@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 88e8ec1b3e372dc1ea1cd0be44c59ca7760e9008 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: 88e8ec1b3e372dc1ea1cd0be44c59ca7760e9008 Allow multiple occurrences of the frames-invalid annotation in gdb.cp/annota2.exp Hi, I see one fail on aarch64-linux testing, FAIL: gdb.cp/annota2.exp: watch triggered on a.x (timeout) because GDB prints two frames-invalid annotation but the test expects only one. next^M ^M ^Z^Zpost-prompt^M ^M ^Z^Zstarting^M ^M ^Z^Zframes-invalid^M ^M ^Z^Zframes-invalid^M ^M Note I also see the fail on Debian-s390x-m64 too. https://sourceware.org/ml/gdb-testers/2015-q4/msg07291.html The test shouldn't only expect one frames-invalid annotation, because there can be multiple times of stop/resume before the user visible stop. Ulrich did something similar before https://www.sourceware.org/ml/gdb-patches/2009-06/msg00118.html This patch only changes ${frames_invalid} to \(${frames_invalid}\)* in the regexp pattern. The patch below fixes the fail on aarch64-linux. gdb/testsuite: 2015-11-27 Yao Qi <yao.qi@linaro.org> * gdb.cp/annota2.exp: Allow multiple occurrences of the frames-invalid annotation.
next reply other threads:[~2015-11-27 14:39 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-27 14:44 sergiodj+buildbot [this message] 2015-11-27 14:39 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2015-11-27 15:00 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2015-11-27 15:08 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2015-11-27 15:24 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-11-27 15:40 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2015-11-27 16:50 ` Failures on Debian-i686, " sergiodj+buildbot 2015-11-27 17:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-11-27 17:28 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-11-30 20:42 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-11-30 20:44 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2015-11-30 20:57 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-11-30 20:57 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-11-30 20:58 ` Failures on Fedora-x86_64-cxx-build-m64, " sergiodj+buildbot 2015-11-30 20:59 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-11-30 21:05 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-11-30 21:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2015-11-30 21:11 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2015-12-06 11:10 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2015-12-06 11:11 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-12-06 11:45 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2015-12-06 12:28 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-12-06 14:43 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-12-06 14:58 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2015-12-06 14:59 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " 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=88e8ec1b3e372dc1ea1cd0be44c59ca7760e9008@gdb-build \ --to=sergiodj+buildbot@redhat.com \ --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).