Skip to content

chore: bump triton pin to 2062702ea69d - #631

Merged
jackalcooper merged 4 commits into
mainfrom
agent/upstream-pins-2062702ea69d
Aug 12, 2026
Merged

chore: bump triton pin to 2062702ea69d#631
jackalcooper merged 4 commits into
mainfrom
agent/upstream-pins-2062702ea69d

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Tracks the latest OpenAI LLVM (llvm/eudsl) release and the latest Triton pin.

  • triton_ref: 2062702ea69d77cf3b39c32a2eb87cb6b889d0d9
  • llvm/eudsl latest asset: mlir_manylinux_x86_64_20260809+9813315f2.tar.gz

The triton-prebuilt-2062702ea69d release was built from this branch before opening the PR, so the Elixir CI can download it. Merging also triggers Build Triton prebuilt (push to main with triton.json), which is idempotent.

The pin PR's Elixir CI downloads triton-prebuilt-<ref> from a release; the
previous design opened the PR first, so the release did not exist yet and
the triton CI job failed with 'release not found' (the chicken-and-egg
between the pin PR and the prebuilt build).

The tracker now:
- checks the Triton-pinned LLVM archive is actually downloadable
  (OpenAI's LLVM builds lag Triton main; skip pins whose LLVM is not out);
- pushes the pin branch, dispatches Build Triton prebuilt on it, and waits
  for the build to finish;
- only then opens the pin PR, whose CI can download the release.

Also drops the redundant triton_ref from upstream-pins.json (triton.json is
the single source of truth; the tracker reads it from there).
When the latest Triton main has not moved since a previous run, the pin
branch already exists remotely and the tracker's push was rejected. Rebuild
the branch from current main and force-push; if a PR for that head already
exists, update its body instead of creating a duplicate.
@github-actions
github-actions Bot force-pushed the agent/upstream-pins-2062702ea69d branch from 4b9848a to 2b242e4 Compare August 12, 2026 00:30
jackalcooper and others added 2 commits August 12, 2026 08:33
GITHUB_TOKEN cannot create workflow_dispatch events (HTTP 403), so the
tracker cannot dispatch the build. Convert triton-prebuilt.yml to a
reusable workflow (workflow_call with an optional triton_ref input) and
have the tracker call it directly for the new pin before opening the pin
PR. The build runs with the caller's token, so no PAT with Actions: write
is required; the pin branch is force-updated from main and an existing
pin PR is reused (body edited) instead of duplicating.
Latest triton-lang/triton main: 2062702ea69d77cf3b39c32a2eb87cb6b889d0d9. Latest llvm/eudsl asset: mlir_manylinux_x86_64_20260809+9813315f2.tar.gz.
@github-actions
github-actions Bot force-pushed the agent/upstream-pins-2062702ea69d branch from 2b242e4 to ebaced0 Compare August 12, 2026 00:33
@jackalcooper
jackalcooper merged commit 0c8bdc3 into main Aug 12, 2026
13 checks passed
@jackalcooper
jackalcooper deleted the agent/upstream-pins-2062702ea69d branch August 12, 2026 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants