Update to nixos 25.05 and OmpSs-2 2025-06 #5
2 Participants
Due Date
No due date set.
Blocks
#6 Update paraver to 4.12.0
rarias/bscpkgs
Reference: rarias/bscpkgs#5
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "update-ompss-2025-06"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upgrades nixpkgs to NixOS 25.05 using the same commit we use in jungle for the system packages. It also upgrades OmpSs-2 packages to the latest release.
Unfortunately, GPI-2 (GASPI) is failing to build due to a missing definition in rdma-core. It can be fixed, but for now I will drop GPI-2 and TAGASPI. See #7
Fixes #8 and #9
Flake lock file updates: • Updated input 'nixpkgs': 'path:/nix/store/2csx2kkb2hxyxhhmg2xs9jfyypikwwk6-source?lastModified=1736867362&narHash=sha256-i/UJ5I7HoqmFMwZEH6vAvBxOrjjOJNU739lnZnhUln8%3D&rev=9c6b49aeac36e2ed73a8c472f1546f6d9cf1addc' (2025-01-14) → 'path:/nix/store/zk8v61cpk1wprp9ld5ayc1g5fq4pdkwv-source?lastModified=1752436162&narHash=sha256-Kt1UIPi7kZqkSc5HVj6UY5YLHHEzPBkgpNUByuyxtlw%3D&rev=dfcd5b901dbab46c9c6e80b265648481aafb01f8' (2025-07-13)Managed to fix all packages and tests (ignoring GPI-2 and TAGASPI).
WIP: Update to nixos 25.05 and OmpSs-2 2025-06to Update to nixos 25.05 and OmpSs-2 2025-06@ -14,3 +14,3 @@, libfabric, gcc, gcc13, gcc7We can probably remove
gcc7Also
linuxHeaders,symlinkJoinandncurses@ -411,3 +414,3 @@icx-wrapper = wrapIntel rec {cc = intel-compiler;mygcc = gcc;mygcc = gcc13;It may be cleaner to put
gcc = gcc13in the top level let and leave all thewrapIntelcalls as is.1c56367446tof0afa10462LGTM
f0afa10462tofece91e756I missed this, it actually fails on rebase because I added tagaspi in bench6. I will need to drop it from the inputs as well.
Also lmbench fails:
fece91e756to24326d4fceSorry for the noise, should be good now:
24326d4fceto974bb56dc3Merged in
974bb56dc3, not sure why Gitea sometimes is not able to detect it.Do we have autodetect enabled in the repo?
If so, maybe we can enable the manual merge option which to my understanding allows to mark the PR as merged by telling gitea which commit merged it
Oops, I had those options disabled, I enabled them. In jungle they were already enabled, maybe that's why it was working there. Thanks!