-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Failure on 32-bit Fedora/RHEL nightlies #9107
Comments
I can't reproduce this. It might be specific to the build flags you're using on Fedora, or maybe the system libraries you're using (LLVM maybe?). |
This is with system LLVM 3.4 and 3.5. All libraries are the system's, gcc is 4.8. You can see the flags in the above link, but nothing fancy. Ah, with LLVM 3.5 the stracktrace is much better:
So looks like it's related to random numbers. @rfourquet? |
Ah yes, there have been a bunch of changes there recently. See the recently added RNG label https://github.com/JuliaLang/julia/issues?q=label%3ARNG+. I wonder whether any of those changes involve the way we build dsfmt? You package that library separately right? |
Right. |
We only patch dsfmt to change a few static methods to extern so that they can be called. Cc @rfourquet |
Ah, so this means I need to export them from Fedora's dSFMT too. Will have a look. |
@nalimilan Could you tell for which value(s) of |
@rfourquet Actually my reading of the backtrace was wrong. So the real failing call is Line 252 in 4045c52
|
I also suspected
It reproduces the conditions of the random tests WRT |
@rfourquet The test in your comment passes. But I don't think the problem is related to |
@nalimilan so this can be closed? |
Right. |
The Fedora/RHEL nightlies fail on 32-bit since 2014-11-21 (last good build happened on 2014-11-19 at 18:48 UTC):
http://copr-be.cloud.fedoraproject.org/results/nalimilan/julia-nightlies/fedora-20-i386/julia-0.4.0-0.20141121.el7.centos/build.log
EDIT: the last successful build was not one, but two days before
The text was updated successfully, but these errors were encountered: