pytorch - 💡(How to fix) Fix [Triton pin 44c91e532420] CI failure tracker

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…
  • Total failures tracked: 40
  • Open: 39
  • Resolved: 1

Root Cause

  • Total failures tracked: 40
  • Open: 39
  • Resolved: 1

Fix Action

Fix / Workaround

  • (build, linux-jammy-py3.14-clang18 / build-osdc)logs

  • (build, linux-jammy-py3.10-gcc11-mobile-lightweight-dispatch-build / build-osdc)logs

  • (build, linux-jammy-py3.10-clang18 / build-osdc)logs

  • (build, linux-jammy-py3.10-clang18-asan / build-osdc)logs

  • (build, linux-jammy-py3.10-gcc11 / build-osdc)logs

  • (build, linux-jammy-aarch64-py3.10 / build-osdc)logs

  • (build, linux-jammy-py3.10-gcc11-no-ops / build-osdc)logs

  • (build, linux-jammy-py3.14t-clang18 / build-osdc)logs

  • linux-jammy-py3.14-clang18 / test (default, 4, 5, linux.4xlarge)logs

  • (infra, lintrunner-noclang-all / lint)logs — fixed by D000000000

RAW_BUFFERClick to expand / collapse
<!-- triton-pin-tracker: 44c91e5324206c54eb10c11581491a01599ebce1 -->

Triton pin update CI tracker — pin 44c91e532420

Pin: 44c91e5324206c54eb10c11581491a01599ebce1 PyTorch PR: #183775 Last updated: 2026-05-15 00:47 UTC

Summary

  • Total failures tracked: 40
  • Open: 39
  • Resolved: 1

Open failures by backend

NVIDIA (20)

  • (build, linux-jammy-cuda13.0-cudnn9-py3.10-clang18 / build-osdc)logs
  • linux-jammy-cuda13.0-py3.10-gcc11-sm100 / test (smoke_b200, 1, 1, linux.dgx.b200)logs
  • inductor-test / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • inductor-test / test (inductor_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • inductor-test / test (inductor_timm, 2, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • inductor-test / test (inductor_timm, 1, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • inductor-test / test (inductor_huggingface, 1, 1, linux.g5.4xlarge.nvidia.gpu)logs
  • unit-test / inductor-test / test (inductor_cpp_wrapper, 2, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • unit-test / inductor-test / test (inductor, 1, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • unit-test / inductor-test / test (inductor_distributed, 1, 1, linux.g5.12xlarge.nvidia.gpu)logs
  • unit-test / inductor-test / test (inductor, 2, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • unit-test / inductor-test / test (inductor_cpp_wrapper, 1, 2, linux.g5.4xlarge.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11-sm86 / test (slow, 2, 3, linux.g5.4xlarge.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11-sm86 / test (slow, 3, 3, linux.g5.4xlarge.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11-sm86 / test (slow, 1, 3, linux.g5.4xlarge.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11 / test (aoti_cross_compile_for_windows, 1, 1, linux.g6.4xlarge.experimental.nvidia.gpu, win-vs2022-...logs
  • linux-jammy-cuda13.0-py3.10-gcc11 / test (default, 5, 5, linux.g6.4xlarge.experimental.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11 / test (default, 1, 5, linux.g6.4xlarge.experimental.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu)logs
  • linux-jammy-cuda13.0-py3.10-gcc11 / test (default, 4, 5, linux.g6.4xlarge.experimental.nvidia.gpu)logs

ROCM (1)

  • (build, linux-jammy-rocm-py3.10 / build-osdc)logs

XPU (1)

  • (build, linux-noble-xpu-n-py3.10 / build-osdc)logs

CPU (9)

  • (build, linux-jammy-py3.14-clang18 / build-osdc)logs
  • (build, linux-jammy-py3.10-gcc11-mobile-lightweight-dispatch-build / build-osdc)logs
  • (build, linux-jammy-py3.10-clang18 / build-osdc)logs
  • (build, linux-jammy-py3.10-clang18-asan / build-osdc)logs
  • (build, linux-jammy-py3.10-gcc11 / build-osdc)logs
  • (build, linux-jammy-aarch64-py3.10 / build-osdc)logs
  • (build, linux-jammy-py3.10-gcc11-no-ops / build-osdc)logs
  • (build, linux-jammy-py3.14t-clang18 / build-osdc)logs
  • linux-jammy-py3.14-clang18 / test (default, 4, 5, linux.4xlarge)logs

UNKNOWN (8)

  • (build, dynamo-cpython-build / build-osdc)logs
  • (test, Test collect_env (older_python_version, linux.24_04.4x))logs
  • (test, Test collect_env (without_torch, linux.24_04.4x))logs
  • (workflow_level, Get changed files / get-changed-files)logs
  • (workflow_level, get-label-type / runner-determinator)logs
  • (test, Test run_test.py is usable without boto3)logs
  • (test, Test collect_env (with_torch, linux.24_04.4x))logs
  • dynamo-test (3.11) / test (dynamo_wrapped, 3, 3, linux.c7i.2xlarge)logs

Resolved failures by backend

CPU (1)

  • (infra, lintrunner-noclang-all / lint)logs — fixed by D000000000

Auto-generated by Meta-internal triton-pin-ci-board tracking. The body refreshes when re-synced; comment if you'd like a status update or have context on a specific failure. (Meta engineers: to attribute a fix, add Fix: D12345678 or Fix: <github-pr-url> to the GSD card description before closing.)

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