pytorch - 💡(How to fix) Fix Remove Bazel build rules from CI [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#180469Fetched 2026-04-17 08:22:17
View on GitHub
Comments
1
Participants
2
Timeline
35
Reactions
3
Author
Participants
Timeline (top)
subscribed ×24labeled ×6mentioned ×2added_to_project_v2 ×1
RAW_BUFFERClick to expand / collapse

🐛 Describe the bug

Or update the to a more modern bazel, as right now it's less and less compatible with the upstream, for example https://github.com/pytorch/cpuinfo/pull/345 renders cpuinfo bazel definition no longer compatible with bazel-4 that rest of the PyTorch use

I propose to delete them, as, to the best of my knowledge nobody ever used those

Versions

2.11/nightly

cc @seemethere @pytorch/pytorch-dev-infra

extent analysis

TL;DR

Update Bazel to a more modern version to ensure compatibility with upstream dependencies.

Guidance

  • Review the compatibility issues with the current Bazel version and upstream dependencies, such as the one mentioned in the PyTorch cpuinfo pull request.
  • Consider deleting unused Bazel definitions to simplify the build process and reduce potential compatibility issues.
  • Verify the compatibility of the updated Bazel version with the rest of the PyTorch project.
  • Test the build process with the updated Bazel version to ensure that it works as expected.

Notes

The issue lacks specific technical details about the current Bazel version and the proposed update, so the guidance is general and focused on the compatibility aspect.

Recommendation

Apply workaround: Update Bazel to a version compatible with the rest of the PyTorch project, such as Bazel-4, to ensure compatibility with upstream dependencies.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING