-
Notifications
You must be signed in to change notification settings - Fork 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
deepspeed.ops.op_builder.async_io.AsyncIOBuilder assert #1037
Comments
@stas00, if you still have the log can you please check if the assert message is preceded by warning like this: |
I was given just this part of the trace, so I don't have access to the full log, but as we discussed here: #998 (comment) it must have been the case. Clearly, the users don't connect the warning and the traceback. Hence the suggestion to include the explicit requirements in the error message. |
Got it. Okay, this will require a bit more code in the JIT engine. We will look into that. |
Perhaps there is a way to check if Looking at the contents of the package, other than .so and .a objects, there is I'm pretty sure I also saw cases of this problem where the WARNING came several lines after the traceback! Different streams... |
same issue, libaio-dev couldnt make it.. |
Why does deepspeed say it works in windows when it obviously does not! |
How can we make it clear to the user that they need to do
apt install libaio-dev
in this assert?@tjruwase, can't we just say
apt install libaio-dev
in the error message?The text was updated successfully, but these errors were encountered: