Repository navigation
Conversation
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
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.
Security fix: supplied device and test-script YAML can execute Python with the benchmark runner’s permissions. Replace unsafe object construction in all three configuration inputs. This also fixes inline device configuration on modern PyYAML.
Validation: three unittest cases passed, covering inline/file equivalence, shipped scripts, and rejection of executable tags. Parsing tests require no hardware drivers.
The new secret-free CI workflow runs these regressions on Python 3.10 and 3.12; both jobs and the CLA check now pass. Sparse checkout avoids unrelated benchmark assets.