This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [testsuite] Run guality tests on Solaris
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>, gcc-patches at gcc dot gnu dot org, Alexandre Oliva <aoliva at redhat dot com>, Mike Stump <mikestump at comcast dot net>
- Date: Fri, 30 Jan 2015 09:19:14 +0100
- Subject: Re: [testsuite] Run guality tests on Solaris
- Authentication-results: sourceware.org; auth=none
- References: <yddlhknjc4e dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <54C949C7 dot 9080902 at redhat dot com> <20150128204635 dot GB1746 at tucnak dot redhat dot com> <yddk306lfe3 dot fsf at CeBiTec dot Uni-Bielefeld dot DE> <54CB2080 dot 7070106 at redhat dot com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Jan 29, 2015 at 11:11:12PM -0700, Jeff Law wrote:
> > Linux/x86_64 Solaris 11/x86 Solaris 11/SPARC
> > (Fedora 20)
> >
> >gcc.dg/guality:
> >
> ># of expected passes 6490 6500 5489
> ># of unexpected failures 191 171 802
> ># of unexpected successes 61 66 73
> ># of expected failures 35 30 23
> ># of unsupported tests 257 267 383
> >
> >g++.dg/guality:
> >
> ># of expected passes 128 128 118
> ># of unexpected failures 6 10 10
> ># of unsupported tests 34 30 40
> Could we select a version of gdb as a reference version, then xfail those
> tests which don't work with that reference version on each platform to cut
> down the noise? Obviously we bump the reference version, probably as we
> close stage1 or stage3 development?
The biggest problem is that what fails and what does not varries between
targets and between optimization levels. Right now we have no way to xfail
test XYZ for -Os on x86_64-linux and for -O2 and -O3 on i686-linux ia32, and
the lists would become very large. Some tests in guality are xfaileded just
in case, even when they actually XPASS on many targets.
The way to look for regressions in the guality area, at least as I do it
regularly, is just compare test_summary results.
If we'd disable this by default, I'm sure our debug quality would sink very
quickly.
Jakub