Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make check failure in linalg #1853

Closed
stevengj opened this issue Dec 30, 2012 · 5 comments
Closed

make check failure in linalg #1853

stevengj opened this issue Dec 30, 2012 · 5 comments
Labels
test This change adds or pertains to unit tests

Comments

@stevengj
Copy link
Member

cd test && make gives:

JULIA test/default
 * default
 * core
 * numbers
 * strings
 * unicode
 * corelib
 * hashing
 * remote
 * iostring
 * arrayops
 * linalg
BoundsError()
  in check_bounds at abstractarray.jl:75
  in check_bounds at abstractarray.jl:110
  in ref at array.jl:326
  in \ at linalg_dense.jl:505
  in anonymous at no file:31
  in include_from_node1 at util.jl:244
  in reload_path at util.jl:254
  in require at util.jl:223
  in runtests at ./runtests.jl:7
  in include_from_node1 at util.jl:244
  in reload_path at util.jl:254
  in require at util.jl:223
  in runtests at ./runtests.jl:7
  in anonymous at no file:46
  in include_from_node1 at util.jl:244
  in process_options at client.jl:199
  in _start at client.jl:255
 at /home/stevenj/cvs/julia/test/linalg.jl:98

(On Debian GNU/Linux x86-64 with gcc 4.4.5.)

PS. Would be nice if the toplevel supported the usual 'make check' target to run the testsuite.

@JeffBezanson
Copy link
Member

This is probably due to the 64-bit blas interface change. Doing make
distclean-{openblas,random,arpack,suitesparse} in deps and rebuilding fixed
this for me.
On Dec 30, 2012 5:35 PM, "Steven G. Johnson" notifications@github.com
wrote:

cd test && make gives:

JULIA test/default

  • default
  • core
  • numbers
  • strings
  • unicode
  • corelib
  • hashing
  • remote
  • iostring
  • arrayops
  • linalg
    BoundsError()
    in check_bounds at abstractarray.jl:75
    in check_bounds at abstractarray.jl:110
    in ref at array.jl:326
    in \ at linalg_dense.jl:505
    in anonymous at no file:31
    in include_from_node1 at util.jl:244
    in reload_path at util.jl:254
    in require at util.jl:223
    in runtests at ./runtests.jl:7
    in include_from_node1 at util.jl:244
    in reload_path at util.jl:254
    in require at util.jl:223
    in runtests at ./runtests.jl:7
    in anonymous at no file:46
    in include_from_node1 at util.jl:244
    in process_options at client.jl:199
    in _start at client.jl:255
    at /home/stevenj/cvs/julia/test/linalg.jl:98

(On Debian GNU/Linux x86-64 with gcc 4.4.5.)

PS. Would be nice if the toplevel supported the usual 'make check' target
to run the testsuite.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1853.

@stevengj
Copy link
Member Author

Yup, that fixes it for me.

@DigitalPig
Copy link

Hi,

I have encountered the same issue here. Even I did the distclean procedure. I still have the problem:

JULIA test/default
 * default
 * core
 * numbers
 * strings
 * unicode
 * corelib
 * hashing
 * remote
 * iostring
 * arrayops
 * linalg

ERROR: BoundsError()
in check_bounds at abstractarray.jl:74
in check_bounds at abstractarray.jl:109
in ref at array.jl:327
in \ at linalg_dense.jl:491
in anonymous at no file:25
in include_from_node1 at loading.jl:76
in runtests at /home/digitalpig/Coding/julia/test/runtests.jl:6
in include_from_node1 at loading.jl:76
in runtests at /home/digitalpig/Coding/julia/test/runtests.jl:6
in anonymous at no file:22
in include_from_node1 at loading.jl:76
in process_options at client.jl:244
in _start at client.jl:307
at /home/digitalpig/Coding/julia/test/linalg.jl:120
at /home/digitalpig/Coding/julia/test/default.jl:13
at /home/digitalpig/Coding/julia/test/runtests.jl:23
make[1]: *** [default] Error 1
make: *** [test] Error 2

I am using Ubuntu 12.10 amd64. I use Julia Ubuntu PPA (#1451). I have already cleaned up all deps and update my source tree...

Thank you.

@ViralBShah
Copy link
Member

You should either use the PPA or build from source. How come you are doing both? Are you using the PPA for the dependencies only?

@DigitalPig
Copy link

Yes. I think the ppa is just for dependency. You still have to build julia from the source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test This change adds or pertains to unit tests
Projects
None yet
Development

No branches or pull requests

4 participants