public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ciro.santilli at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/18067] many failures in testsuite Date: Wed, 22 Jul 2015 12:40:00 -0000 [thread overview] Message-ID: <bug-18067-4717-kCkp7GVlHR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18067-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18067 Ciro Santilli <ciro.santilli at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ciro.santilli at gmail dot com --- Comment #2 from Ciro Santilli <ciro.santilli at gmail dot com> --- I was getting 388 failures on tag binutils-2_25, Ubuntu 14.04 GCC 4.8 the large majority related to attach. Then I run with: sudo make check RUNTESTFLAGS="--ignore bigcore.exp" and it fell down to 36 only! I ignore bigcore.exp because it slows my machine too much: https://sourceware.org/bugzilla/show_bug.cgi?id=18704 So it seems that the inability to attach without sudo was the cause of most failures. We should really document that somewhere. @Keith: - why don't we mark failing tests with XFAIL so as to unclutter the tests? - shouldn't we document about the sudo on the testsuite/README ? - I am unable to find the buildbot results for a given commit to compare, e.g. binutils-2_25... is that possible? Not built-in it seems: https://groups.google.com/a/chromium.org/forum/#!topic/infra-dev/T_7S9HXLWlo Attaching .sum and .log. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-22 12:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-02 13:31 [Bug testsuite/18067] New: " yuri at tsoft dot com 2015-03-17 19:19 ` [Bug testsuite/18067] " keiths at redhat dot com 2015-07-22 12:40 ` ciro.santilli at gmail dot com [this message] 2015-07-22 12:48 ` ciro.santilli at gmail dot com 2015-07-23 9:41 ` palves at redhat dot com 2015-07-31 11:46 ` ciro.santilli at gmail dot com
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=bug-18067-4717-kCkp7GVlHR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).