Skip to content

feat: add support for 26.05.x - #426

Closed
giovtorres wants to merge 1 commit into
mainfrom
26.05.x
Closed

feat: add support for 26.05.x#426
giovtorres wants to merge 1 commit into
mainfrom
26.05.x

Conversation

@giovtorres

Copy link
Copy Markdown
Member

This change adds support for Slurm 26.05.

@chriswasser

Copy link
Copy Markdown

cross-comment from #424: your new branch with commit 6242fad works on for my monitoring use cases on our cluster 👌

just two comments:

  • You switched your versioning / branch name scheme to include the leading zero from SLURM's versioning (previously: 25.5.x for 25.05.x, now: 26.05.x for 26.05.x). Not a huge deal, but just wanted to mention this (potentially breaking) change as it might be worth to include in the CHANGELOG.
  • In the future, I would love to see SLUID support within pyslurm since SLURM itself seems to have adapted these unique identifiers more thoroughly now. Compared to the previous JobIDs that could reset at some point (and even be reused for multiple restarts of the same job in case of node failures), SLUIDs finally offer a simple unique key for external database storage. Of course, this feature would not block the general release of pyslurm 26.05.x, but I just wanted to add something to the wishlist 😇

Thanks for providing an official 26.05.x compatible branch so quickly 🙏

@giovtorres giovtorres closed this Aug 25, 2026
@giovtorres
giovtorres deleted the 26.05.x branch August 25, 2026 22:04
@giovtorres

Copy link
Copy Markdown
Member Author

Thank you for that callout. I renamed the branch to 26.5.x to match the existing pattern. I just ended up opening another PR: #427

@giovtorres

Copy link
Copy Markdown
Member Author

Also, im not familiar with SLUID, but I’ll take a look and see. Thanks for suggesting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants