| 24 Jun 2024 |
connor (he/him) | Gaétan Lepage: ran into an error doing the build
$ cat ~/.config/nixpkgs/config.nix
{
allowAliases = false;
allowBroken = false;
allowUnfree = true;
checkMeta = true;
cudaCapabilities = [ "7.5" ];
cudaSupport = true;
}
$ nix build --impure -L github:GaetanLepage/nixpkgs/jax#python311Packages.jaxlibWithCuda
https://gist.github.com/ConnorBaker/56253dd716f7b0a30705916cff13f964
| 02:48:45 |
Gaétan Lepage | Thanks for taking the time connor (he/him) (UTC-5).
I actually wanted you to try my jaxlib branch.
The jax branch is for the jax update and it is basically stuck becaus of some important changes in the upstream packaging/build process | 06:27:56 |
hexa | In reply to @hexa:lossy.network it keeps clogging my hydra build slots alot also not a fan of deepwave and qutip | 10:10:47 |
hexa |
https://hj.9fs.net/emery/p/1719216291.477930
| 10:10:57 |
hexa | *
"Wave propagation modules for PyTorch"
| 10:11:12 |
hexa |
"Open-source software for simulating the dynamics of closed and open quantum systems"
| 10:11:27 |
SomeoneSerge (back on matrix) | "Not just an infra problem" | 10:14:54 |
hexa | what are you quoting? | 10:20:20 |
connor (he/him) | In reply to @glepage:matrix.org Thanks for taking the time connor (he/him) (UTC-5).
I actually wanted you to try my jaxlib branch.
The jax branch is for the jax update and it is basically stuck becaus of some important changes in the upstream packaging/build process I tried but didn’t see a jaxlib branch :/ | 12:51:28 |
Gaétan Lepage | Oh indeed, I deleted it after the PR was merged. | 13:09:03 |
connor (he/him) | Sorry I didn’t get to it sooner, my bad :( | 13:19:45 |
connor (he/him) | Gaétan Lepage: you mentioned you had a wrapper (script?) around Nixpkgs-review which ran it with different configurations. Any chance you can share it? I’ve been wanting to have some way to have Nixpkgs-review generate an expression for everything it would build, parameterized by multiple Nixpkgs configs. | 13:21:40 |
Gaétan Lepage | In reply to @connorbaker:matrix.org Sorry I didn’t get to it sooner, my bad :( No worry ! | 13:29:52 |
Gaétan Lepage | In reply to @connorbaker:matrix.org Gaétan Lepage: you mentioned you had a wrapper (script?) around Nixpkgs-review which ran it with different configurations. Any chance you can share it? I’ve been wanting to have some way to have Nixpkgs-review generate an expression for everything it would build, parameterized by multiple Nixpkgs configs. Yes, I have a script which start nixpkgs-review for several architectures at once.
My plan long term is to contribute to upstream for being able to run the tool for several architectures at once and have a single message posted on the PR | 13:31:20 |
Gaétan Lepage | Link: https://github.com/GaetanLepage/nix-config/blob/master/home/modules/tui/dev/nix/review.sh | 13:31:22 |
Gaétan Lepage | https://github.com/GaetanLepage/nix-config/blob/91a5a77f1bcfb779dbe4daa86702de8c5483c19e/home/modules/tui/dev/nix/default.nix#L16-L23 | 13:31:39 |
connor (he/him) | Every time I try to contribute I get distracted by something in my periphery and go down a different rabbit hole :/
I definitely want to improve the markdown output (to better support multi-line nixpkgs configs) and find a way to do evaluation faster. | 13:43:43 |
Gaétan Lepage | Yes, on one of my PRs you have put some very fancy markdown outputs.
Also, I noticed that natsukium was providing a link to each failing build log, that's very cool | 14:39:09 |
SomeoneSerge (back on matrix) | In reply to @hexa:lossy.network what are you quoting? I can't remember exactly, but there was a moment when joked along the lines of "that's what hydra is for" in relation to some mildly nasty test suite 🙃 | 15:16:20 |
| 26 Jun 2024 |
hexa | SomeoneSerge (UTC+3): how would you describe the current situation of the cuda maintainers cache? | 01:05:54 |
hexa | * SomeoneSerge (UTC+3): how would you describe the current state of the cuda maintainers cache? | 01:06:02 |