[ FAILED ] prob_transform.ordered_j (0 ms) about stan HOT 8 CLOSED

original author: goodrich.ben

Thank you for this report. What version of what C++ compiler were you using?

from stan.

original author: normvcr

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-redhat-linux/4.7.2/lto-wrapper
Target: i686-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --disable-build-with-cxx --disable-build-poststage1-with-cxx --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch=i686 --build=i686-redhat-linux
Thread model: posix
gcc version 4.7.2 20120921 (Red Hat 4.7.2-2) (GCC)

from stan.

Project Member [email protected]

Is this the only unit test that failed? If so, it's easy to fix by changing the significant digits on the test, which indeed seems to be the main issue.

The compilers do vary in basic arithmetic operations.

Ben -- did you want to run some tests under linux to see if you can recreate the test failure?

from stan.

goodrich.ben

It passes for me (Debian) with g++ 4.7.x and clang 3.1.x, so I would say to just relax the test.

from stan.

normvcr

This was the only test that failed.
I suppose it is a source code change to relax the test.
I am happy to test an update when it is ready.
Thanks for checking into this.

from stan.

[email protected]

Thanks for the update. We'll fix it in the next release. I'll close this issue with the Git hash code for the commit that fixes it. Your report's enough for the fix.

from stan.

Migrated from google code: http://code.google.com/p/stan/issues/detail?id=70

from stan.

I'm closing this issue -- we must have fixed it with one of our patches.

from stan.