GSL polynomial tests are failing

[bugproxy]

---Problem Description---
GSL polynomial tests are failing

---uname output---
Linux lep8d 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23 16:18:35 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = P8

---Steps to Reproduce---
Install a P8 Non Virtualized machine with Ubuntu 15.04 ISO.
Then install the GNU Scientific Library sources on the same.

root@lep8d:~# wget http://gnumirror.nkn.in/gsl/gsl-1.16.tar.gz

root@lep8d:~# tar -xvf gsl-1.16.tar.gz
root@lep8d:~# cd gsl-1.16/
root@lep8d:~/gsl-1.16# ls
aclocal.m4 ChangeLog COPYING gsl gsl.pc.in INSTALL min ode-initval siman test_gsl_histogram.sh
AUTHORS cheb depcomp gsl-config.in gsl_pow_int.h install-sh missing ode-initval2 sort THANKS
autogen.sh combination deriv gsl-histogram.c gsl_precision.h integration mkinstalldirs permutation specfunc TODO
blas complex dht gsl_inline.h gsl-randist.c interpolation monte pkgconfig.test statistics utils
block config.guess diff gsl.m4 gsl.spec.in linalg multifit poly sum vector
bspline config.h.in doc gsl_machine.h gsl_types.h ltmain.sh multimin qrng sys version.c
BUGS config.sub eigen gsl_math.h gsl_version.h Makefile.am multiroots randist templates_off.h wavelet
build.h configure err gsl_minmax.h gsl_version.h.in Makefile.in multiset README templates_on.h
cblas configure.ac fft gsl_mode.h histogram matrix NEWS rng test
cdf const fit gsl_nan.h ieee-utils mdate-sh ntuple roots test-driver

root@lep8d:~/gsl-1.16# ./configure
root@lep8d:~/gsl-1.16# make

root@lep8d:~/gsl-1.16# make check

root@lep8d:~/gsl-1.16# cat poly/test-suite.log
===================================
   gsl 1.16: poly/test-suite.log
===================================

# TOTAL: 1
# PASS: 0
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test
==========

FAIL: z1.real, 15th-order polynomial (-1.00000000000000044 observed vs 1 expected) [159]
FAIL: z2.real, 15th-order polynomial (1.00000003899845002 observed vs -1 expected) [161]

Userspace tool common name: glibc

The userspace tool has the following bit modes: 64-bit

Userspace rpm: glibc-2.21

> root@lep8d:~/gsl-1.16# cat poly/test-suite.log
> ===================================
> gsl 1.16: poly/test-suite.log
> ===================================
>
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0

I don't see this happening on Launchpad: https://launchpadlibrarian.net/191125448/buildlog_ubuntu-vivid-ppc64el.gsl_1.16%2Bdfsg-2build1_UPLOADING.txt.gz

What happens if you use the same source code provided by Canonical and the configure flags used by them?

There are many tests being not executed if we build how Canonical has build gsl.

The below mentioned tests are getting executed the way we build :
(./configure; make and make check )

gsl-1.16/linalg
gsl-1.16/eigen
gsl-1.16/specfunc
gsl-1.16/dht
gsl-1.16/qrng
gsl-1.16/rng
gsl-1.16/randist
gsl-1.16/fft
gsl-1.16/poly

Don't know why Canonical is not executing these tests which should have been.

Looks like a known bug in gsl 1.16

https://savannah.gnu.org/bugs/?40176

Cloned the latest gsl code from git repo ( git clone git://git.savannah.gnu.org/gsl.git )
and make check passes on poly directory..
Please verify.

I have executed the tests again on my system with the latest git tree source of gsl.

root@powerkvmpok002:~# git clone git://git.savannah.gnu.org/gsl.git
Cloning into 'gsl'...
remote: Counting objects: 47578, done.
remote: Compressing objects: 100% (8261/8261), done.
remote: Total 47578 (delta 39275), reused 47554 (delta 39261)
Receiving objects: 100% (47578/47578), 12.53 MiB | 3.75 MiB/s, done.
Resolving deltas: 100% (39275/39275), done.
Checking connectivity... done.

root@powerkvmpok002:~# cd gsl/
root@powerkvmpok002:~/gsl# ./autogen.sh
If you use a recent version of autotools, this script is obsolete
Just run autoreconf -i -f -v
followed by ./configure --enable-maintainer-mode

configure.ac:91: installing './compile'
configure.ac:87: installing './config.guess'
configure.ac:87: installing './config.sub'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
doc/Makefile.am:3: installing 'doc/mdate-sh'
Now use ./configure --enable-maintainer-mode

root@powerkvmpok002:~/gsl# ./configure --enable-maintainer-mode
root@powerkvmpok002:~/gsl# make
root@powerkvmpok002:~/gsl# make check

root@powerkvmpok002:~/gsl# cd poly/
root@powerkvmpok002:~/gsl/poly# make check
make test
make[1]: Entering directory '/root/gsl/poly'
gcc -DHAVE_CONFIG_H -I. -I.. -I.. -g -O2 -MT test.o -MD -MP -MF .deps/test.Tpo -c -o test.o test.c
mv -f .deps/test.Tpo .deps/test.Po
/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test test.o libgslpoly.la ../ieee-utils/libgslieeeutils.la ../err/libgslerr.la ../test/libgsltest.la ../sys/libgslsys.la ../utils/libutils.la ../sort/libgslsort.la -lm
libtool: link: gcc -g -O2 -o test test.o ./.libs/libgslpoly.a ../ieee-utils/.libs/libgslieeeutils.a ../err/.libs/libgslerr.a ../test/.libs/libgsltest.a ../sys/.libs/libgslsys.a ../utils/.libs/libutils.a ../sort/.libs/libgslsort.a -lm
make[1]: Leaving directory '/root/gsl/poly'
make check-TESTS
make[1]: Entering directory '/root/gsl/poly'
make[2]: Entering directory '/root/gsl/poly'
PASS: test
make[3]: Entering directory '/root/gsl/poly'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/gsl/poly'
============================================================================
Testsuite summary for gsl 1.16+
============================================================================
# TOTAL: 1
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
make[2]: Leaving directory '/root/gsl/poly'
make[1]: Leaving directory '/root/gsl/poly'

Can we request Ubuntu to incorporate the latest version of the gsl source from the git tree provided ==> git clone git://git.savannah.gnu.org/gsl.git

So that this new sources can be incorporated and all failures will get fixed.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1439753/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]