Skip to content

chore: move vllm-xpu-run to intel/gpu-ai-skills@6e7bce819e2e - #81

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
sync/vllm-xpu-run-44f2158b2ccc
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
sync/vllm-xpu-run-44f2158b2ccc

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

vllm-xpu-run has changed in intel/gpu-ai-skills on main and this repository's copy of it has not. Opened by tools/check_upstream.py; the bytes are upstream's at the new commit, written by tools/sync_external.py --write.

  • pin: 0b4fafd09c5eb4cc5daf532d915ef5984a919775 -> 6e7bce819e2e44a4aac692b0a49253f39c0f6957
  • upstream diff: intel/gpu-ai-skills@0b4fafd...6e7bce8
  • also changed upstream, each in its own pull request: model-can-it-fit, model-config-recommend, torch-xpu-bench, vllm-xpu-bench, vllm-xpu-profile

Merge or close this one on its own. Closing it declines this version of vllm-xpu-run: it is not proposed again, and the next change upstream is.

What this does not decide is whether the new text should be merged. An import is somebody else's document, so a change in it is a change somebody made there: the checks below answer the structural half, and the diff is worth reading.

If the checks are waiting for approval, this pull request was opened with GITHUB_TOKEN: select Approve workflows to run in the merge box to start them.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants