Skip to content

[COMPAT] Pin Triton to 3.8 - #527

Closed
mark14wu wants to merge 1 commit into
mainfrom
compat/pin-triton-3.8
Closed

mark14wu wants to merge 1 commit into
mainfrom
compat/pin-triton-3.8

Conversation

@mark14wu

@mark14wu mark14wu commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

Triton 3.9.0 is out, and triton>=3.8.0 now resolves to it. TileLens has only been tested on Triton 3.8: the eager clients patch private interpreter APIs, and the IR clients in the stack on top of main (#479 and up) support 3.8 only, so on 3.9 every IR launch is reported unsupported. Until 3.9 is supported, this keeps installs and CI on 3.8.

Change

  • pyproject.toml: triton>=3.8.0 → triton>=3.8.0,<3.9.
  • CI (python-app.yml, benchmark.yml): install triton==3.8.0 and triton_kernels at v3.8.0 instead of --pre -U triton and triton_kernels from Triton's main branch, which made CI test whatever Triton was newest. Set UV_NO_SYNC=1 at job level so uv run does not re-sync the environment and undo the pin. These workflow hunks are identical to the ones [FEAT] Add the host-compiled IR lifecycle for clients #479 already carries, so merging main into the stack stays conflict-free.

Tests

  • uv pip compile pyproject.toml --python-version 3.12 resolves triton==3.8.0.
  • CI on this PR runs the suites on Triton 3.8.0.

Triton 3.9.0 is out, and `triton>=3.8.0` now installs it. TileLens has
only been tested on 3.8: the eager clients patch private interpreter APIs,
and the IR clients being added on top of main support 3.8 only. Until 3.9
is supported, cap the dependency below 3.9.

CI installed `--pre -U triton` and triton_kernels from Triton's main
branch, so it was running against whatever Triton was newest. Install
Triton 3.8.0 and triton_kernels at v3.8.0 instead, and set UV_NO_SYNC so
`uv run` does not re-sync the environment and undo the pin. The workflow
changes are the same as the ones the IR stack already carries.
@mark14wu mark14wu closed this Nov 7, 2026
@mark14wu

mark14wu commented Nov 7, 2026

Copy link
Copy Markdown
Collaborator Author

Closed. Duplicate of #530.

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.

1 participant