Bugzilla Bug 213359

sci-libs/umfpack-5.2.0 fails tests on ppc64

Portage 2.1.4.4 (default-linux/ppc/ppc64/2007.0/64bit-userland/desktop/power3,
gcc-4.1.2, glibc-2.6.1-r0, 2.6.24.3 ppc64)
=================================================================
System uname: 2.6.24.3 ppc64 POWER3 (630+)
Timestamp of tree: Thu, 13 Mar 2008 09:00:01 +0000
app-shells/bash:     3.2_p17-r1
dev-java/java-config: 1.3.7, 2.1.4
dev-lang/python:     2.4.4-r9, 2.5.1-r5
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 2.0.0_rc6-r1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.23-r3
ACCEPT_KEYWORDS="ppc64"
CBUILD="powerpc64-unknown-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="powerpc64-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/kde/4.0/env /usr/kde/4.0/share/config
/usr/kde/4.0/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf
/etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/
/etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild
/etc/terminfo /etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer nostrip sandbox sfperms strict
unmerge-orphans userfetch"
GENTOO_MIRRORS="http://192.168.0.2/ http://gentoo.virginmedia.com/"
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --stats --timeout=180 --exclude=/distfiles
--exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac acl alsa apache2 archive arts berkdb bzip2 cairo captury cdr cli
cracklib crypt ctype cups curl d dbus dri dts dvd dvdr eds emboss encode esd
espeak exif fam firefox flac fortran gcj gd gdbm gif glib glitz gnome gnutls
gpgme gpm gstreamer gtk hal ibm iconv imap imlib inotify ipv6 isdnlog jack jpeg
jpeg2k kde latex ldap libffi libnotify mad mdnsresponder-compat midi mikmod mp2
mp3 mp4 mpeg mudflap mysql ncurses nls nptl nptlonly objc objc++ objc-gc ogg
openal openexr opengl openmp oss pam pcre pdf perl png ppc64 pppd python qt3
qt3support qt4 quicktime readline reflection science sdl session sidebar smime
smtp spell spl sqlite ssl svg tcpd tetex theora tiff truetype unicode vnc
vorbis x264 xcb xcomposite xine xml xorg xscreensaver xv xvid zip zlib"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file
hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route
share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias
authn_anon authn_dbm authn_default authn_file authz_dbm authz_default
authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs
dav_lock deflate dir disk_cache env expires ext_filter file_cache filter
headers include info log_config logio mem_cache mime mime_magic negotiation
rewrite setenvif speling status unique_id userdir usertrack vhost_alias"
ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses
text" USERLAND="GNU" VIDEO_CARDS="dummy fbdev mach64 mga nv r128 radeon vega"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS,
MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS,
PORTDIR_OVERLAY

Created an attachment (id=146094) [details]
umfpack build.log

Hi Markus,

Thanks for the heads-up!

Unfortunately, the tests fail on my opteron as well 
so these may actually be faulty test routines. We should
probably contact upstream and ask them what's up
with that.

Best,
Markus

I contacted upstream. The difference you see in the logs are difference in
round offs and are fine. So you can go ahead and keyword it.

Now I will try to convince upstream to update the regression test to make them
more robust.

added ~ppc64

(In reply to comment #3)
> I contacted upstream. The difference you see in the logs are difference in
> round offs and are fine. So you can go ahead and keyword it.
> 
> Now I will try to convince upstream to update the regression test to make them
> more robust.
> 

Why not RESTRICT="test" in the meantime?

I'd rather remove the offending tests from the test suite
since the rest seems to work fine.