Draft
Conversation
hasAlloc was only ever false, so it could never trigger JobStatusDead
tgross
reviewed
Jul 15, 2025
Comment on lines
5514
to
5516
| // The job is dead if all allocations for this version are terminal, | ||
| // all evals are terminal. In the event a jobs allocs and evals | ||
| // are all GC'd, we don't want the job to be marked pending. |
Member
There was a problem hiding this comment.
The second sentence here appears to be accurate, but the first sentence no longer is because we're not considering terminal vs GC'd allocs. We should probably update this language and the language in the comment at the bottom of the function.
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
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.
hasAlloc was only ever false, so it could never return JobStatusDead
Or perhaps #25081 should have re-added
hasAlloc = truelike it was in #24974? Checking with @mismithhislerDescription
Testing & Reproduction steps
Links
Contributor Checklist
changelog entry using the
make clcommand.ensure regressions will be caught.
and job configuration, please update the Nomad website documentation to reflect this. Refer to
the website README for docs guidelines. Please also consider whether the
change requires notes within the upgrade guide.
Reviewer Checklist
backporting document.
in the majority of situations. The main exceptions are long-lived feature branches or merges where
history should be preserved.
within the public repository.