-
Notifications
You must be signed in to change notification settings - Fork 150
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
Error while executing using StaticArrays
on nightly
#291
Comments
What happens with precompilation turned off? |
With <lots of deprecation warnings>
SYSTEM: show(lasterr) caused an error
ArgumentError("No StaticArray found in argument list")
Stacktrace:
[1] include_relative(::Module, ::String) at ./loading.jl:464
[2] include at ./sysimg.jl:14 [inlined]
[3] include(::String) at /Users/twan/code/julia/RigidBodyDynamics/v0.7/StaticArrays/src/StaticArrays.jl:3
[4] include_relative(::Module, ::String) at ./loading.jl:464
[5] _require(::Symbol) at ./loading.jl:401
[6] require(::Symbol) at ./loading.jl:318
[7] eval(::Module, ::Expr) at ./repl/REPL.jl:3
[8] eval_user_input(::Any, ::Base.REPL.REPLBackend) at ./repl/REPL.jl:69
[9] macro expansion at ./repl/REPL.jl:100 [inlined]
[10] (::Base.REPL.##1#2{Base.REPL.REPLBackend})() at ./event.jl:73 and Julia doesn't crash. Does anybody else experience this issue? |
Hmm. It would be nice to somehow have a more nuanced view of failure on Travis. I decided to allow failures on 0.7, because they're quite distracting for normal feature development. Especially in a package like |
I am able to reproduce this on Ubuntu.
|
FWIW this is making development of JuliaStats packages difficult on 0.7, since StaticArrays is usually a dependency of a dependency. Let me know if there's anything I can do to help with this. |
I'm actually unable to reproduce Julia not crashing, as tkoolen was able to do by turning off precompilation... |
@ararslan if you have time for some investigation, you could try hunting down all occurrences of signatures like used in #282. If I had to guess what's going on here, I'd say our signature has broken generic |
OK, I merged the |
Yep, I've confirmed that this fixes the original issue. Thanks! |
I'm getting an error even before #283 now.
The text was updated successfully, but these errors were encountered: