This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug testsuite/18067] many failures in testsuite
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 23 Jul 2015 09:41:00 +0000
- Subject: [Bug testsuite/18067] many failures in testsuite
- Auto-submitted: auto-generated
- References: <bug-18067-4717 at http dot sourceware dot 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.