-
Notifications
You must be signed in to change notification settings - Fork 342
[CI]Enable CI for TorchAO on XPU Using Docker #3027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/3027
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 Cancelled JobAs of commit a42e14b with merge base 8e2ca35 ( CANCELLED JOB - The following job was cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Warning: Unknown label
Please add the new label to .github/pytorch-probot.yml |
@pytorchbot label "ciflow/xpu" |
Warning: Unknown label
Please add the new label to .github/pytorch-probot.yml |
@pytorchbot label "ciflow/xpu" |
Warning: Unknown label
Please add the new label to .github/pytorch-probot.yml |
@pytorchbot label "ciflow/xpu" |
@pytorchbot label "ciflow/xpu" |
Warning: Unknown label
Please add the new label to .github/pytorch-probot.yml |
@pytorchbot label "ciflow/xpu" |
Warning: Unknown label
Please add the new label to .github/pytorch-probot.yml |
@pytorchbot label "ciflow/xpu" |
Warning: Unknown label
Please add the new label to .github/pytorch-probot.yml |
This PR aims to enable the CI pipeline for TorchAO targeting the XPU architecture. By leveraging Docker, we have streamlined the setup process, ensuring a consistent and isolated environment that closely mimics production settings. This approach not only facilitates easier debugging but also enhances our ability to promptly gate and block potential issues before they affect the broader codebase. Key improvements and features introduced in this PR include:
Docker Environment Setup
Integration with Existing CI/CD Pipeline
Trigger Mechanism