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] Skip attach-many-short-lived-threads.exp on known-broken DejaGnu versions Date: Fri, 27 May 2016 15:32:00 -0000 [thread overview] Message-ID: <744608cc854a365661e93d307aadf22ab6e6bd7c@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 744608cc854a365661e93d307aadf22ab6e6bd7c *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 744608cc854a365661e93d307aadf22ab6e6bd7c Skip attach-many-short-lived-threads.exp on known-broken DejaGnu versions If the testsuite is run with a DejaGnu version that predates the fix from last year: [PATCH] DejaGnu kills the wrong process due to PID-reuse races http://lists.gnu.org/archive/html/dejagnu/2015-07/msg00005.html ... gdb.threads/attach-many-short-lived-threads.exp fails randomly, often. Other tests randomly fail due to that issue too, but this one is _much_ more exposed. DejaGnu 1.6 was released meanwhile, which includes that DejaGnu fix, and also some distros backported the fix too. So skip the test when run with older/broken DejaGnus. gdb/testsuite/ChangeLog: 2016-05-27 Pedro Alves <palves@redhat.com> * gdb.threads/attach-many-short-lived-threads.exp (bad_dejagnu): New procedure. (top level): Call it, and bail out of DejaGnu is known to be bad.
next reply other threads:[~2016-05-27 15:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-27 15:32 sergiodj+buildbot [this message] 2016-05-27 15:38 ` *** COMPILATION FAILED *** Failures on AIX-POWER7-plain, branch master *** BREAKAGE *** sergiodj+buildbot 2016-05-27 16:45 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot 2016-05-27 17:31 ` Failures on Fedora-i686, " sergiodj+buildbot 2016-05-27 20:10 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2016-05-27 20:37 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-05-27 22:23 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-05-28 2:20 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-05-28 2:35 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2016-05-28 2:36 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2016-05-28 2:54 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2016-05-28 3:05 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-05-28 3:44 ` Failures on Fedora-ppc64be-native-extended-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=744608cc854a365661e93d307aadf22ab6e6bd7c@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).