Add "StartTimeStamp" output in SlurmInfo #38
Conversation
This file contains 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
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.
It is desireable for some purposes to have access to the exact, persistent timestamp that a job started on a machine which may not have access to Slurm or be aware of timezones, datetimeformats, and other configurable factors. The easiest way to achieve this is to simply compute the timestamp directly from "starttime" as this is fetched from scontrol show in SlurmInfo. This PR accomplishes this by adding the entry "starttimestamp".
(This is a feature we have been using for a while, it is important to some time-sensitive things like killing jobs, but I noticed that I hadn't pushed it upstream now when I added some new features.)