Repository navigation
[Chore][Release] Add a release image with TileOPs and TileFoundry, and drop the sgl-kernel baseline - #2793
Conversation
Test planImage
The release layer was built on the published |
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
No image installs sgl-kernel, so bench_moe_permute_align always skipped it and its column never reported a number.
3ddc3fe to
110c73f
Compare
|
The |
f9acaef to
0eaab14
Compare
…m PyPI The release target installs the published tileops and tilefoundry on the dev image, so users get both releases with every benchmark baseline. tilefoundry caps transformers below the lock's pin; an override keeps the lock's version. scripts/verify_release_image.sh pulls the image and checks it on a GPU against the tests and benchmarks of the matching git tag, since the wheel carries neither.
0eaab14 to
0f6313f
Compare
Summary
.github/runner/Dockerfilegains areleasetarget: the dev image plus the PyPI releases of tileops and tilefoundry, named byTILEOPS_VERSIONandTILEFOUNDRY_VERSION.ghcr.io/tile-ai/tileops-release:tileops0.1.0-tilefoundry0.0.3-cuda13.2-torch2.13-tilelang0.1.12; the tag prefixes the dev tag with the two release versions.scripts/verify_release_image.shpulls the image and runs, on a GPU, the stack and baseline checks, the packaging tests and any--benchfile, all taken from the git tag of the image's tileops version, since the wheel carries no tests or benchmarks.bench_moe_permute_alignalways skipped it.