Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
OpenDAS
vllm_cscc
Commits
268a972c
Unverified
Commit
268a972c
authored
Dec 19, 2025
by
Andrey Talman
Committed by
GitHub
Dec 19, 2025
Browse files
Update Pytorch version update docs (#30982)
parent
5fbfa8d9
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
14 deletions
+9
-14
docs/contributing/ci/update_pytorch_version.md
docs/contributing/ci/update_pytorch_version.md
+9
-14
No files found.
docs/contributing/ci/update_pytorch_version.md
View file @
268a972c
...
@@ -77,25 +77,20 @@ This complicates the process as we cannot use the out-of-the-box
...
@@ -77,25 +77,20 @@ This complicates the process as we cannot use the out-of-the-box
-
`.buildkite/release-pipeline.yaml`
-
`.buildkite/release-pipeline.yaml`
-
`.buildkite/scripts/upload-wheels.sh`
-
`.buildkite/scripts/upload-wheels.sh`
##
Address long vLLM build time
##
Manually running vLLM builds on BuildKiteCI
When building vLLM with a new PyTorch/CUDA version, no cache will exist
When building vLLM with a new PyTorch/CUDA version, the vLLM sccache S3 bucket
in the vLLM sccache S3 bucket, causing the build job on CI to potentially take more than 5 hours
will not have any cached artifacts, which can cause CI build jobs to exceed 5 hours.
and timeout. Additionally, since vLLM's fastcheck pipeline runs in read-only mode,
Furthermore, vLLM's fastcheck pipeline operates in read-only mode and does not
it doesn't populate the cache, so re-running it to warm up the cache
populate the cache, making it ineffective for cache warm-up purposes.
is ineffective.
While ongoing efforts like
<https://github.com/vllm-project/vllm/issues/17419>
To address this, manually trigger a build on Buildkite to accomplish two objectives:
address the long build time at its source, the current workaround is to set
`VLLM_CI_BRANCH`
to a custom branch provided by @khluu (
`VLLM_CI_BRANCH=khluu/long_build`
)
when manually triggering a build on Buildkite. This branch accomplishes two things:
1.
Increase the timeout limit to 10 hours so that the build doesn't time out.
1.
Run the complete test suite against the PyTorch RC build by setting the environment variables:
`RUN_ALL=1`
and
`NIGHTLY=1`
2.
Allow the compiled artifacts to be written to the vLLM sccache S3 bucket
2.
Populate the vLLM sccache S3 bucket with compiled artifacts, enabling faster subsequent builds
to warm it up so that future builds are faster.
<p
align=
"center"
width=
"100%"
>
<p
align=
"center"
width=
"100%"
>
<img
width=
"60%"
alt=
"Buildkite new build popup"
src=
"https://github.com/user-attachments/assets/
a8ff0fcd-76e0-4e91-b72f-014e3fdb6b94"
>
<img
width=
"60%"
alt=
"Buildkite new build popup"
src=
"https://github.com/user-attachments/assets/
3b07f71b-bb18-4ca3-aeaf-da0fe79d315f"
/
>
</p>
</p>
## Update all the different vLLM platforms
## Update all the different vLLM platforms
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment