runtime/lava: fix string priority fallback in _get_priority#3053
Merged
nuclearcat merged 1 commit intokernelci:mainfrom Feb 18, 2026
Merged
Conversation
bhcopeland
force-pushed
the
fix/lava-priority-string-fallback
branch
from
71cfd75 to
33d65f2
Compare
The job.config.priority fallback path did not handle string values (e.g. "medium", "high") from YAML job configs, causing a TypeError when the value reached the priority scaling arithmetic. Signed-off-by: Ben Copeland <ben.copeland@linaro.org>
bhcopeland
force-pushed
the
fix/lava-priority-string-fallback
branch
from
33d65f2 to
03be1f6
Compare
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
2 participants
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.
The job.config.priority fallback path did not handle string values (e.g. "medium", "high") from YAML job configs, causing a TypeError when the value reached the priority scaling arithmetic.
Run string values through priority_map, matching the handling already done for tree_priority and user_priority paths.
This will allow us to revert 5550ae05a940058c95a0f773226c99695c7bea92