[Bug go/56432] New: libgo check should behave like the check target for all other target libraries

[doko at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56432



             Bug #: 56432

           Summary: libgo check should behave like the check target for

                    all other target libraries

    Classification: Unclassified

           Product: gcc

           Version: 4.8.0

            Status: UNCONFIRMED

          Severity: normal

          Priority: P3

         Component: go

        AssignedTo: i...@airs.com

        ReportedBy: d...@gcc.gnu.org





the libgo testsuite unfortunately works not the same as all other testsuites

for the target libraries do work. Usually if you do want to test a multilib

build, you call



  RUNTESTFLAGS="--target_board=unix\{,-m32,-mx32\}" make -k check



and only the check target for the default multilib is called. The check target

doesn't descend into the multilib directories. libgo however descends into the

non-default multilib targets and calls check there too. And then with the above

RUNTESTFLAGS, every go test is called nine times instead of three times, and

apparently fails the other six times.



Otoh, running the test without RUNTESTFLAGS, and having at least a multilib

which can't be run on the current kernel, tries to run all multilib

configurations, and fails every test in these (this is a common use case on

build daemon machines running kernels of an older release).



Please let libgo behave the same as the other target libraries for the check

target, even it does introduce some delta.