-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
"Internal compiler error: too many bits types" when running testall #5688
Comments
I can verify this problem on Linux. julia> versioninfo()
Julia Version 0.3.0-prerelease+1399
Commit 20b9453* (2014-02-05 16:27 UTC)
Platform Info:
System: Linux (x86_64-linux-gnu)
CPU: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz
WORD_SIZE: 64
BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY)
LAPACK: libopenblas
LIBM: libopenlibm |
(I've updated the issue accordingly.) |
It seems unlikely that that commit caused the issue, but rather uncovered it. Having 2-processors/cores also seems to be a prerequisite to trigger this. Travis doesn't have a problem (it runs with 8 procs), and the tests run fine on an 8-core machine I tried. Artificially restricting to 2 processors there caused the error to appear. |
I get almost the same problem on Linux, but it only observed it when I run the tests in serial (i.e. setting |
I have this problem on OSX 10.9. I'm on a late 2010 macbook air. |
This is very strange. Here (Fedora 20 64-bit) it only happens with double-conversion 2.0.1. With the version I was using previously, 2.0.0, the tests run fine. I've tested several times and always got this result. By chance, would you be using a recent release of double-conversion 1.x or 2.x? |
I ran with all the libraries as pulled in by the julia install, which is in this case double-conversion 1.1.1. |
Which test ran before in the same worker? For example I get after deactivating some tests
but
|
Forget about double-conversion, I eventually got tests to pass with 2.0.1. |
@loladiro @vtjnash How about we simply clear the |
I would like to see why it happens first (perhaps instrument the fn with printf) |
If it's memory corruption, your proposal probably wouldn't fix it |
My proposal isn't intended to fix any possible memory corruption; it's just a related observation that this error is avoidable in case it ever happens for real. |
Looks like |
Oh my goodness how did we miss that. Thank you. |
The fix solves the issue for me, now |
Recently, I have had problems with running
make testall
on my mac. After a while the output goes crazy withThe tests work when I run them individually. It is a mid 2009 MacBook Pro and
versioninfo()
isThe text was updated successfully, but these errors were encountered: