[Bug build/20967] Several Tests failed on MIPS64 N64

["carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=20967

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2016-12-14
     Ever confirmed|0                           |1

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
Known failures are listed here for glibc 2.24:
https://sourceware.org/glibc/wiki/Release/2.24

FAIL: conform/UNIX98/sys/socket.h/conform
FAIL: conform/XOPEN2K/arpa/inet.h/conform
FAIL: conform/XOPEN2K/netdb.h/conform
FAIL: conform/XOPEN2K/netinet/in.h/conform
FAIL: conform/XOPEN2K/sys/socket.h/conform
FAIL: conform/XOPEN2K8/arpa/inet.h/conform
FAIL: conform/XOPEN2K8/netdb.h/conform
FAIL: conform/XOPEN2K8/netinet/in.h/conform
FAIL: conform/XOPEN2K8/sys/socket.h/conform
FAIL: conform/XPG4/sys/socket.h/conform

Can you look to see what these errors are? There should be matching *.out file
in your build directory for each of these which explains why the conform test
fails. Usually these are benign because they don't immediately impact core
functionality, but will cause problems in some more complex applications.

FAIL: elf/check-execstack
FAIL: elf/check-localplt
FAIL: elf/tst-execstack
FAIL: elf/tst-execstack-needed

These are serious security issues and toolchain configuration issues. Either a
misconfiguration or a bootstrap with an executable stack (bad). Might be one
object which is being added from the compiler which has the wrong attributes.

FAIL: math/test-double
FAIL: math/test-double-finite
FAIL: math/test-float
FAIL: math/test-float-finite
FAIL: math/test-idouble
FAIL: math/test-ifloat

Could be compiler issues or hardware issues. You have to look at the *.out
files to see if your errors are all off by 1 or 2 ULPS then it's just a case
that your hardware might be slightly less precise and so the expected error set
needs to be adjusted a bit for your given hardware. That patch could go
upstream.

FAIL: nptl/tst-cancel24-static

Could be anything. Maybe related to unwind information or compiler issues
generating the right unwind information to cancel the thread in the test. Look
at the *.out file again.

FAIL: nptl/tst-execstack
FAIL: nptl/tst-stack4

Potentially related to the above execstack failures.

FAIL: posix/tst-getaddrinfo4
FAIL: posix/tst-getaddrinfo5

Probably harmless and related to your networking configuration e.g. can you
reach the internet or not.

The failures don't look terrible, not the best, and they indicate some tooling
issues, but not terrible. Your system will probably run.

I'll move this to WAITING for you to respond with some results of looking at
the *.out files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.