Repository navigation
Pull request/19 - #19
Merged
Merged
Conversation
Signed-off-by: Aung San aka Mike <41126828+aung-san-i@users.noreply.github.com>
* xpu heterogeneous test * fix PR_NUMBER finding * write log to a separate folder * strip_ansi from Dynamo's Rust tracing logger * if fail, upload pods logs * check exit code of vllm bench serve in bench pod * check error signature in the logs and exit if there is --------- Signed-off-by: Aung San aka Mike <41126828+aung-san-i@users.noreply.github.com>
The XPU vLLM base image bumped from ee0da84...-xpu (digest 22b2291f) to 0e28fde...-xpu (digest b24859c2). The new base ships level-zero and level-zero-devel, whose .debs carry no /usr/share/doc/*/copyright file, so the DEP-5 parser falls through to UNKNOWN and the license policy gate denies level-zero-devel@1.28.2. Recapture the self-baseline SBOM from the new image so its level-zero components are subtracted from the final-image NOTICES, and repoint context.yaml's baseline_sbom at it. Layer-prefix verified (19/19), delta 0, all delta components pass policy. Drop the orphaned 22b2291f baseline (SBOM file + manifest entry). Also add version-agnostic MIT license overrides for level-zero and level-zero-devel (upstream oneapi-src/level-zero is MIT) so patch bumps of the base image stay covered even outside the subtracted baseline. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
Point the xpu-heterogeneous-dispatch default xpu_base_image_tag at the current base image (0e28fde...-xpu) instead of the retired ee0da84...-xpu. The input overrides BASE_IMAGE_TAG/RUNTIME_IMAGE_TAG/WHEEL_BUILDER_IMAGE at build time, so leaving the old default would build a dispatched XPU image against the previous base and contradict context.yaml and the refreshed baseline SBOM. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
The current XPU base image no longer bakes `source setvars.sh` into its ENV, and Dynamo resets ENTRYPOINT to [] so nothing sources it at runtime. As a result XPU devices are not detected without a manual `source setvars.sh`. Bake the oneAPI variables setvars.sh provides (OCL_ICD_FILENAMES, CMPLR_ROOT, ONEAPI_ROOT, plus the compiler/mpi bin and oneAPI lib dirs) into the XPU runtime stage so an empty-entrypoint container detects XPUs directly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
Update the XPU vLLM base/runtime image from 0e28fde…-xpu (digest b24859c2, vLLM 0.23.1rc1.dev1165) to 1582e816cb…-xpu (digest 15ff6ee4, vLLM 0.23.1rc1.dev1401) in context.yaml. Recapture the self-baseline SBOM from the new image so the licenses stage subtracts the correct floor from the final-image NOTICES, and repoint context.yaml's baseline_sbom at it. Layer-prefix verified (19/19), delta 0, all delta components pass policy; level-zero/level-zero-devel present. Drop the orphaned b24859c2 baseline (SBOM file + manifest entry). oneAPI component versions in the new image are unchanged (compiler 2025.3, ccl/mpi 2021.15), so the XPU device-detection ENV block needs no update. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
Point the xpu-heterogeneous-dispatch default xpu_base_image_tag at the new XPU base image (1582e816cb…-xpu) so a dispatched build's BASE_IMAGE_TAG/ RUNTIME_IMAGE_TAG/WHEEL_BUILDER_IMAGE match context.yaml and the refreshed baseline SBOM. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
Update the XPU vLLM base/runtime image from 1582e816cb…-xpu (digest 15ff6ee4) to 752a3a50…-xpu (digest 26109489) in context.yaml. Recapture the self-baseline SBOM from the new image so the licenses stage subtracts the correct floor from the final-image NOTICES, and repoint context.yaml's baseline_sbom at it. Layer-prefix verified (19/19), delta 0, all delta components pass policy; level-zero/level-zero-devel 1.28.2 present. Drop the orphaned 15ff6ee4 baseline (SBOM file + manifest entry). oneAPI component versions in the new image are unchanged (compiler 2025.3, ccl/mpi 2021.15), so the XPU device-detection ENV block needs no update. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
Point the xpu-heterogeneous-dispatch default xpu_base_image_tag at the new XPU base image (752a3a50…-xpu) so a dispatched build's BASE_IMAGE_TAG/ RUNTIME_IMAGE_TAG/WHEEL_BUILDER_IMAGE match context.yaml and the refreshed baseline SBOM. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sandeep Maddipatla <sandeep.maddipatla@intel.com>
Signed-off-by: Sandeep Maddipatla <mmsandeep@gmail.com>
Signed-off-by: Aung San aka Mike <41126828+aung-san-i@users.noreply.github.com>
…ld is submitted blank
aung-san-i
had a problem deploying
to
external_collaborator
August 7, 2026 03:49 — with 
GitHub Actions
Failure
GitHub Actions
Failure
aung-san-i
added a commit
that referenced
this pull request
Sep 16, 2026
* ci(xpu): re-apply XPU pre-merge and heterogeneous EPD CI onto upstream main Re-applies the CI portion of fork PRs #18, #19 and #20 (squash commits 937d0ee, bce72a9, 8845cd9) on top of upstream main 9fcc771, after the fork was synced to ai-dynamo/dynamo and those three commits were discarded from main. Conflict resolution in .github/workflows/pr-xpu.yaml: kept the inline build-xpu job instead of upstream's new xpu-ci-vllm reusable-workflow call. The heterog-test-px-dn / heterog-test-pn-dx jobs consume needs.build-xpu.outputs.image, and .github/workflows/xpu-ci.yaml declares no workflow_call outputs, so the built image tag cannot be threaded through it. Upstream's call site also reads "uses: $/.github/workflows/xpu-ci.yaml", which is not a valid local reusable-workflow path. Also fixes a syntax error that was present on the old fork main: the pn-dx.yaml case in .github/scripts/test-filters.js was missing its closing brace, so the file did not parse. node --check now passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * container(xpu): carry over oneAPI env and XPU baseline SBOM from PR #18 Both changes are Sandeep Maddipatla's, originally commits 87e5e8d ("fix(container): set oneAPI env for XPU vLLM runtime device detection") and a402586 ("fix(compliance): bump XPU vLLM base image and refresh baseline SBOM"). They were swept into fork main by the #18 squash merge, which attributed them to the PR author. Isolated here in their own commit because both need review against current upstream before merging: - container/templates/vllm_runtime.Dockerfile sets ONEAPI_ROOT=/opt/intel/oneapi plus hardcoded compiler/2025.3, mpi/2021.15 paths. Upstream's current template carries a comment in the same {% if device == "xpu" %} block warning against exactly this: vLLM 0.27.1's XPU image ships the oneAPI runtime and SYCL headers in /opt/venv via the intel-sycl-rt wheel, the /opt/intel/oneapi tree is removed, and Triton prioritises ONEAPI_ROOT over its wheel-metadata fallback, so it would search a nonexistent compiler include path. The problem the original commit fixed (Dynamo resets ENTRYPOINT to [], so setvars.sh never runs) may still be real, but this mechanism no longer matches the base image. - container/compliance/base_sboms/vllm-ci-test-repo@26109489-amd64.cdx.json is 133095 lines / 22470 components and is referenced by no manifest.json entry. The original commit also bumped manifest.json and container/context.yaml, but later commits in the #18 chain reverted those, leaving this file orphaned. Upstream's manifest.json now points at vllm-openai-xpu@3309c2e1-amd64.cdx.json. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch had an error being deployed
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.
Overview:
Details:
Where should the reviewer start?
Related Issues
🔗 This PR is linked to an issue:
🚫 This PR is NOT linked to an issue: