Fix SLURM account specification: ensure $userstring is correctly parsed by SLURM #376
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This pull request updates the way the SLURM account line ($userstring) is inserted into job scripts.
Previously, using spaces instead of tabs could cause SLURM to ignore or misinterpret the account name, resulting in jobs not being assigned to the correct account.
By ensuring the correct formatting (using tabs or proper variable expansion), SLURM now correctly parses the account name from $userstring.
Summary of changes:
Updated all $userstring insertions in the script to use the correct format for SLURM account parsing.