-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
python312Packages.jax: 0.4.38 -> 0.5.0 #374810
Conversation
Could you also update jax-cuda12-pjrt and jax-cuda12-plugin? |
Sure, done ! |
Getting this failure on Darwin:
There are already disabled tests for jax for the same error, so we should probably add this test case to the list for the platform. |
Yes, I have seen this nanobind failure occuring on several other packages. |
|
For |
Yes. They have some integration tests I think? I've also noticed that Jax test suite hogs a lot of memory (apparently my Linux builder with 20gb RAM is not enough) and swaps until it times out. I see this with the older version too. Perhaps on a related note, nanobind itself fails in test suite for me (on Darwin at least) because jaxlib leaks. Something is really wrong about jax/nanobind combination. |
Yes, there might be some issues of this kind. |
I will retry. Isn't python313Packages.jax in the list of broken packages in your nixpkgs-review output for Darwin too? Do you have logs from the failure? |
I am facing the same
|
b726950
to
3b9ee84
Compare
|
|
I am also running into this (building with Although in my case, since the tests run on cpu anyways (#256230) there isn't much of a point so I just |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but haven't tested.
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should just skip the Jax tests all together?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The jax tests are not too bad. What tends to be unreliable is the tests in other packages that use jax
.
The issue is that so many things are currently broken that it is tedious to separate regressions from overall noise...
|
Things done
cc @samuela @natsukium
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.