-
Notifications
You must be signed in to change notification settings - Fork 193
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
Mix cannot continue when building EXLA #845
Comments
This is weird because it even says at the beginning that the app was compiled defined. What happens if you do |
nothing, no output
see below |
Nothing after the first compilation. Only after the second time, contents appear, including iex -S mix
similar situation with |
@jnnks can you please try this: rm -rf _build
rm -rf deps
mix deps.get
XLA_BUILD=true MIX_ENV=prod mix deps.compile xla
tree _build/prod/lib/xla
XLA_BUILD=true MIX_ENV=prod mix deps.compile exla
tree _build/prod/lib/xla I am suspecting exla compilation is the one erasing it somehow. |
for some reason the first logs
|
Ok, I missed some deps, sorry! it should have been this instead:
maybe complex is not required… but I think XLA will be there on both runs. |
more logs
|
So when does it disappear?!?! Only on “mix compile”? |
Seems like the problem only appears when building XLA from scratch. |
Sounds like it but i was hoping the instructions above could reproduce it. If you finally do a |
Nope, still there :) |
Schrodinger's xla.app. 😄 Thank you for digging deeper! |
Looks like it was in fact deleted during the build process. First Run (fails)XLA_BUILD=true MIX_ENV=prod mix compile
inotifywait -m -r .
Second Run (success)XLA_BUILD=true MIX_ENV=prod mix compile
|
Awesome @jnnks! Can you please post the 100 entries before and after the DELETE? |
Here are the entire logs :D 1st Run: https://gist.github.com/jnnks/88f2cda21064d0bb109a42ec4b701cb2 2nd Run: https://gist.github.com/jnnks/ad8a25419b3d84a6cef83b9892a926e3 |
@jonatanklosko so this is caused by the explicit |
Lines 26 to 29 in 2769f4a
Without that, |
I think we will have to remove the |
The config would only handle Updating the docs sounds good, though this change may cause some confusion for people relying on |
The issue is only with |
The EXLA build fails with:
Full Log
Happens with
{:exla, "~> 0.2"}
on a new project. The compilation seems to work fine though. XLA service is initialized and StreamExecutor can find a device.No error is raised for subsequent compiles.
The text was updated successfully, but these errors were encountered: