8000 UNSTABLE pull / linux-jammy-xpu-2025.0-py3.9 / build · Issue #150430 · pytorch/pytorch · GitHub
[go: up one dir, main page]
Skip to content

UNSTABLE pull / linux-jammy-xpu-2025.0-py3.9 / build #150430

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.

Sign up for GitHub

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

Jump to bottom
Closed
malfet opened this issue Apr 1, 2025 · 2 comments
Closed

UNSTABLE pull / linux-jammy-xpu-2025.0-py3.9 / build #150430

malfet opened this issue Apr 1, 2025 · 2 comments
Assignees
@chuanqi129
Labels
module: ci Related to continuous integration triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module unstable

Comments

@malfet
Copy link
Contributor
malfet commented Apr 1, 2025 •
edited by pytorch-bot bot
Loading

It started to fail after a PR that did not touch anything related to XPUs were landed see https://hud.pytorch.org/hud/pytorch/pytorch/783f045c4f26cb9d11789d80f68a86854dfad9f9/1?per_page=50&name_filter=xpu&mergeLF=true

cc @seemethere @pytorch/pytorch-dev-infra
@pytorch-bot pytorch-bot bot added module: ci Related to continuous integration unstable labels Apr 1, 2025
@pytorch-bot PyTorch Bot
Copy link
pytorch-bot bot commented Apr 1, 2025
Hello there! From the UNSTABLE prefix in this issue title, it looks like you are attempting to unstable a job in PyTorch CI. The information I have parsed is below:
  • Job name: pull / linux-jammy-xpu-2025.0-py3.9 / build
  • Credential: malfet

Within ~15 minutes, pull / linux-jammy-xpu-2025.0-py3.9 / build and all of its dependants will be unstable in PyTorch CI. Please verify that the job name looks correct. With great power comes great responsibility.

@malfet malfet added triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module and removed module: ci Related to continuous integration unstable labels Apr 1, 2025
@pytorch-bot pytorch-bot bot added module: ci Related to continuous integration unstable labels Apr 1, 2025
@clee2000 clee2000 moved this to Prioritized in PyTorch OSS Dev Infra Apr 1, 2025
@clee2000 clee2000 moved this from Prioritized to Cold Storage in PyTorch OSS Dev Infra Apr 1, 2025
@chuanqi129
Copy link
Collaborator

This issue caused by PR #149888 landed without false-positive xpu build test signal (due to issue #149995). And it exposed due to oneAPI DLE 2025.0 has released patch version, which fixed the issue #149995. And we're working on the xpu commit pin update by PR #150409 to resolve this issue completely.

@xytintel xytintel mentioned this issue Apr 2, 2025
Closed
@chuanqi129 chuanqi129 self-assigned this Apr 2, 2025
@chuanqi129 chuanqi129 mentioned this issue Apr 2, 2025
Closed
@github-project-automation github-project-automation bot moved this from Cold Storage to Done in PyTorch OSS Dev Infra Apr 2, 2025
amathewc pushed a commit to amathewc/pytorch that referenced this issue Apr 17, 2025
@chuanqi129 @amathewc
Update torch-xpu-ops commit pin to 98c808d (pytorch#150554)
c937d1e 
Update the torch-xpu-ops commit to [98c808dea6de7330c415aa777d6921944cf79887](intel/torch-xpu-ops@98c808d), include

- Fixes pytorch#150001 by removing pre-CXX11 ABI logic from build script for XPU
- Fixes pytorch#150430
- Fixes XCCL build issue caused by PR pytorch#150398

Pull Request resolved: pytorch#150554
Approved by: https://github.com/EikanWang, https://github.com/malfet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chuanqi129 chuanqi129

Labels
module: ci Related to continuous integration triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module unstable
Projects
PyTorch OSS Dev Infra
Archived in project
Milestone
No milestone
2 participants
@malfet @chuanqi129
0