Created attachment 748538 [details]
glibc make check out file

Kumuda,

What problem are you looking at, or what issue have you run into that you are looking at the testsuite results?

Very few, if any, targets ever pass the glibc testsuite cleanly. There are kernel interactions to consider along with known issues in the implementation.

There is only a problem if the testsuite regresses from release to release (between y-stream releases e.g. 7.0 to 7.1).

Do you have a specific problem that you have encountered?

------- Comment From kumuda.govind.com 2013-05-16 10:40 EDT-------
This bug is filed to check on the reported compilation errors, as there were no reports found for the listed failures except math/test-ldouble.out.

(In reply to comment #0)
> == Comment: #0 - Kumuda G <kumuda.govind.com> - 2013-05-15 06:30:40 ==
> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
> nptl/tst-cancel24-static] Error 1
> make[1]: *** [nptl/tests] Error 2
> make[2]: ***

Install libstdc++-static to make this one go.

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/rt/
> tst-mqueue5.out] Error 1

It's one of those timing sensitive tests that fails every now and then.

> make[2]: ***
> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
> rtkaio/tst-cpuclock2.out] Error 1

Likewise.

> make[2]: ***
> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
> rtkaio/tst-cputimer1.out] Error 1

Likewise.

(In reply to IBM Bug Proxy from comment #1)
> Created attachment 748538 [details]
> glibc make check out file

BTW, the make output itself is useless here.  What we would need along with the make output are the *.out files for the tests that failed.

------- Comment From kumuda.govind.com 2013-05-22 11:01 EDT-------
(In reply to comment #13)
> (In reply to IBM Bug Proxy from comment #1)
> > Created attachment 748538 [details]
> > glibc make check out file
>
> BTW, the make output itself is useless here.  What we would need along with
> the make output are the *.out files for the tests that failed.

Below is the contents of out file for failed tests...

> math/test-ldouble.out] Error 1
# cat math/test-ldouble.out
testing long double (without inline functions)
Failure: Real part of: clog (0x0.fffffffffffff8p0 + 0x0.fffffffffffff8p-1000 i) == -1.110223024625156602053389888482372171810e-16 + 9.332636185032188789900895447238171696171e-302 i: Exception "Underflow" not set
Failure: Real part of: csqrt (0x1p-500 + 0x1p-1074 i) == 5.527147875260444560247265192192255725514e-76 + 4.469444793151709302716387622440056066334e-249 i: Exception "Underflow" set

Test suite completed:
6264 test cases plus 5256 tests for exception flags executed.
2 errors occurred.

> nptl/tst-cleanup2.out] Error 1
# cat nptl/tst-cleanup2.out
Attempting to sprintf to null ptr
Exiting main...

> nptl/tst-cleanupx2.out] Error 1
# cat nptl/tst-cleanupx2.out
Attempting to sprintf to null ptr
Exiting main...

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
out file is empty

# cat rt/tst-mqueue5.out
SIGRTMIN signal in child did not arrive
child failed with status 256

> make[2]: *** No rule to make target `check-abi-librtkaio', needed by
> `check-abi'.

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
> rtkaio/tst-mqueue5.out] Error 1
# cat rt/tst-mqueue5.out
SIGRTMIN signal in child did not arrive
child failed with status 256

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
# cat rtkaio/tst-cpuclock2.out
live thread clock fffffffffffdb7c6 resolution 0.000000001
live thread before sleep => 0.000348034
self thread before sleep => 0.000838840
live thread after sleep => 0.500232374
self thread after sleep => 0.000952966
absolute clock_nanosleep on PROCESS_CPUTIME_ID 18446744073709543628 past target (outside reasonable range)
absolute clock_nanosleep on PROCESS_CPUTIME_ID slept 99992012 (outside reasonable range)

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
# cat rtkaio/tst-cputimer1.out
clock_gettime returned timespec = { 0, 530446 }
clock_getres returned timespec = { 0, 1 }
*** timer sig1 invoked too soon: 0.401458184 instead of expected 0.401662688
*** timer sig2 invoked too soon: 0.501488862 instead of expected 0.501662688

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
> elf/tst-audit2.out] Error 1
# cat elf/tst-audit2.out
version: 1
objopen: 0,
objopen: 0, /root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/elf/ld64.so.1
activity: add
objsearch: libc.so.6, LA_SET_ORIG
objsearch: /root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/libc.so.6, LA_SER_LIBPATH
objopen: 0, /root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/libc.so.6
activity: consistent
symbind64: symname=__libc_start_main, st_value=0x1000004415c0, ndx=2237, flags=0
pltenter: symname=__libc_start_main, st_value=0x1000004415c0, ndx=2237, flags=0
preinit
symbind64: symname=printf, st_value=0x1000004434e8, ndx=634, flags=0
pltenter: symname=printf, st_value=0x1000004434e8, ndx=634, flags=0
symbind64: symname=free, st_value=0x100000444ad0, ndx=2367, flags=0
pltenter: symname=free, st_value=0x100000444ad0, ndx=2367, flags=0
pltenter: symname=free, st_value=0x100000444ad0, ndx=2367, flags=0
objclose
objclose
objclose
{abcdef72, d8675309} != {d8675309, abcdef72}

> [/root/rpmbuild/BUILD/glibc-2.17-c758a686/build-ppc64-redhat-linux-power6/
> elf/check-localplt.out] Error 1
# cat elf/check-localplt.out
Extra PLT reference: libc.so: memset
Extra PLT reference: libc.so: memmove

------- Comment From sjmunroe.com 2013-07-19 14:33 EDT-------
This could be GLIBC or kernel. So need to involve Ryan and Nish to look into the root cause.

Also does state what HW model and if this is a partition with virtual or fractional cores.

------- Comment From sjmunroe.com 2013-07-19 14:34 EDT-------
s/does/does not/

Created attachment 813420 [details]
Results of glibc make check on F20


------- Comment (attachment only) From anmogarg.com 2013-10-17 15:37 EDT-------

(In reply to IBM Bug Proxy from comment #6)
> > math/test-ldouble.out] Error 1
> # cat math/test-ldouble.out
> testing long double (without inline functions)
> Failure: Real part of: clog (0x0.fffffffffffff8p0 + 0x0.fffffffffffff8p-1000
> i) == -1.110223024625156602053389888482372171810e-16 +
> 9.332636185032188789900895447238171696171e-302 i: Exception "Underflow" not
> set
> Failure: Real part of: csqrt (0x1p-500 + 0x1p-1074 i) ==
> 5.527147875260444560247265192192255725514e-76 +
> 4.469444793151709302716387622440056066334e-249 i: Exception "Underflow" set
> 
> Test suite completed:
> 6264 test cases plus 5256 tests for exception flags executed.
> 2 errors occurred.

These were known failures in 2.17:

https://sourceware.org/glibc/wiki/Release/2.17

(In reply to IBM Bug Proxy from comment #8)
> Created attachment 813420 [details]
> Results of glibc make check on F20
> 

Looks like this last test run was clean.  I'll close this bug unless there are any outstanding questions.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.