public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/18067] many failures in testsuite Date: Thu, 23 Jul 2015 09:41:00 -0000 [thread overview] Message-ID: <bug-18067-4717-CmgOgkGZdR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18067-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18067 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #5 from Pedro Alves <palves at redhat dot com> --- > why don't we mark failing tests with XFAIL so as to unclutter the tests? We do - though it's KFAIL for known gdb failures - but it takes someone to actually do the leg work. All help appreciated. > - shouldn't we document about the sudo on the testsuite/README ? I'd welcome a patch. As you found out, it's the ptrace_scope thing that's at play. Running gdb under sudo isn't a good idea. > - 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: Find the git repo for results of the builder you want the results for, then look for a results commit whose subject indicates it tested the gdb commit hash you wanted. Note that most builders are testing master, some the 7.10 branch, so you naturally won't find results for hashes only on other branches. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-23 9:41 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 2015-07-22 12:48 ` ciro.santilli at gmail dot com 2015-07-23 9:41 ` palves at redhat dot com [this message] 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-CmgOgkGZdR@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).