Thanks! That fixes the mod2pi issue. Mysteriously enough, the linalg4
tests are all passing now for me too. (I have no idea how this
happened, as I've started from a clean build each time and none of the
other commits to release-0.3 since v0.3.8 seem to be related; also my
Make.user is identical. There must have been some change in my
environment variables that I am not accounting for.)
On 05/13/2015 07:24 PM, Tony Kelman wrote:
Oh right, give me a minute to
backport 3ab9af16015b23426c0936bbe73a6d4007c32040 then try from latest
release-0.3.
On Wednesday, May 13, 2015 at 7:15:05 PM UTC-7, Jim Garrison wrote:
Other than logdet, the mod2pi tests fail pretty miserably.
Everything
else passes.
On Wed, 2015-05-13 at 14:45 -0700, Jim Garrison wrote:
> Thanks Tony! If I disable the logdet test, everything else in
linalg4
> works. (I'm running the remainder of the test suite now to see if
> anything else errors.) If there's no hope of backporting the
fix, I
> wonder if it makes sense to put a note in the 0.3-release README.
>
> On Wed, 2015-05-13 at 14:34 -0700, Tony Kelman wrote:
> > Which function there is causing trouble? There are a few
> > @test_approx_eq_eps lines that are very similar there, for
det, trace,
> > expm, logdet, and sqrtm. I think logdet has given problems
with Intel
> > compilers in the past. Most likely there's a complex calling
> > convention mismatch that was fixed by some of the ccall rework on
> > master that can't really be backported to release-0.3.
> >
> >
> > On Wednesday, May 13, 2015 at 12:13:24 PM UTC-7, Jim Garrison
wrote:
> > OK, that thread does not seem to apply for me because
I am
> > indeed using ifc as my fortran compiler. My full
Make.user is
> > as follows:
> >
> >
> > MARCH = nehalem
> >
> >
> > USEICC = 1
> > USEIFC = 1
> > USE_INTEL_MKL = 1
> > USE_INTEL_MKL_FFT = 1
> > USE_INTEL_LIBM = 1
> >
> >
> > I get the same error even without the `MARCH =
nehalem` line.
> >
> > On Wednesday, May 13, 2015 at 12:10:19 PM UTC-7, Jim
Garrison
> > wrote:
> > Sorry for the noise; just discovered the thread
> > at https://groups.google.com/forum/#
<https://groups.google.com/forum/#>!
> > searchin/julia-users/linalg4
> > $20icc/julia-users/ZsGhxR0Pd_s/7V4LNjNO0foJ
and will
> > report back if I still have trouble after reading
> > that.
> >
> > On Wednesday, May 13, 2015 at 12:08:41 PM
UTC-7, Jim
> > Garrison wrote:
> > With the merging of #11251, I have been
> > attempting (once again) to get julia 0.3
> > working on a cluster where it has so far
> > resisted working fully. When I
compile master
> > with icc/mkl according to the
instructions in
> > the README, all tests pass. But when
I do the
> > same thing for v0.3.8 (using icc
15.0.2), I
> > get a test failure in linalg4:
> >
> >
> > * linalg4
> > exception on 1: ERROR: assertion
failed: |
> > func(D) - func(DM)| <= 3.4332275e-5
> > func(D) = 1.048798f0 -
1.5707964f0im
> > func(DM) = 1.0487979650497437 -
> > 0.5797938426309308im
> > difference = 0.9910025278753558 >
> > 3.4332275e-5
> > in error at error.jl:22
> > in test_approx_eq at test.jl:109
> > in anonymous at no file:295
> > in runtests
> > at
/home/garrison/julia/v0.3.8-mkl/test/testdefs.jl:5
> > in anonymous at multi.jl:660
> > in run_work_thunk at multi.jl:621
> > in remotecall_fetch at multi.jl:694
> > in remotecall_fetch at multi.jl:709
> > in anonymous at task.jl:1365
> > while loading linalg4.jl, in
expression
> > starting on line 263
> > ERROR: assertion failed: |func(D) -
> > func(DM)| <= 3.4332275e-5
> > func(D) = 1.048798f0 -
1.5707964f0im
> > func(DM) = 1.0487979650497437 -
> > 0.5797938426309308im
> > difference = 0.9910025278753558 >
> > 3.4332275e-5
> > in error at error.jl:22
> > in test_approx_eq at test.jl:109
> > in anonymous at no file:295
> > in runtests
> > at
/home/garrison/julia/v0.3.8-mkl/test/testdefs.jl:5
> > in anonymous at multi.jl:660
> > in run_work_thunk at multi.jl:621
> > in remotecall_fetch at multi.jl:694
> > in remotecall_fetch at multi.jl:709
> > in anonymous at task.jl:1365
> > while loading linalg4.jl, in
expression
> > starting on line 263
> > while
> > loading
/home/garrison/julia/v0.3.8-mkl/test/runtests.jl, in expression
starting on line 38
> >
> >
> > Has anybody else experienced a similar
error?
> >
> >
> > Jim
>
>