Draft: CI/CD pipeline to test reference implementations#2585
Draft
anandhu-eng wants to merge 1 commit into
Draft
Draft: CI/CD pipeline to test reference implementations#2585anandhu-eng wants to merge 1 commit into
anandhu-eng wants to merge 1 commit into
Conversation
Contributor
|
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.
This PR introduces a CI/CD pipeline to test reference implementations. It triggers on PRs raised against the inference repository. The goal is to automatically detect which benchmark is relevant based on the files changed, run it on our self-hosted MLC2 GPU server, and post the results back as a PR comment with an initial approval step.
When a PR is opened:
Inference repo: Automatically detects which folder was modified (e.g. vision/classification_and_detection/yolo/) and dispatches the corresponding benchmark workflow. No extra input from the maintainer needed.
Endpoints repo: Routes based on PR labels (benchmark:llama3, benchmark:all, etc.) added by the maintainer before approval.
TBD in inference repo to change the draft state of the PR
Note:
Currently the worfklow supports yolo benchmark only. More to be added in time