[CI] Force HTTP/1.1 for runtime Git installs - #55044
Merged
Merged
Conversation
GitHub rejects HTTP/2 upload-pack POSTs from the H200 CI image with HTTP 401, causing Hybrid and V1 source installs to hang at an interactive username prompt. Supply Git's documented environment config so those steps use HTTP/1.1 instead.\n\nCo-authored-by: Codex <codex@openai.com> Signed-off-by: Kevin Luu <51931015+khluu@users.noreply.github.com>
Member
Author
|
Targeted exact validation is running in Buildkite #86981 at head
Bootstrap passed and the three exact jobs rendered successfully. Their terminal results—especially the runtime Git installs—are the pre-merge gate. |
ZJY0516
approved these changes
Sep 3, 2026
Member
Author
|
Exact validation is terminal green in Buildkite #86981 at head
This directly covers all three main-CI failure signatures fixed by this PR. The PR is now merged as |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
The failing H200 jobs can fetch public GitHub refs, but Git 2.43/libcurl 8.5 in the CI image sends the upload-pack POST over HTTP/2 and receives HTTP 401. Git then prompts for a username and the job hangs until its 65/80-minute timeout. Host-side Git on the same machines succeeds, so checkout and host egress are not the failing boundary.
The same CI image reproduces the protocol split exactly:
HTTP/2: exit 128,fatal: expected flush after ref listingGIT_CONFIG_COUNT=1,GIT_CONFIG_KEY_0=http.version,GIT_CONFIG_VALUE_0=HTTP/1.1: public tag lookup succeedsRepresentative failures:
Duplicate work
I searched open vLLM PRs and issues for
http.version,HTTP/1.1,expected flush after ref listing,could not read Username, and the Mamba/causal-conv1d install path. I found no open PR addressing this CI transport failure.Validation
h200-ci-4Stepschema and asserted the exact environment mappingpre-commit run --hook-stage pre-commit --files .buildkite/test_areas/models_language.yaml .buildkite/test_areas/misc.yamlpassedgit diff --checkpassedThis contribution was prepared with AI assistance and reviewed line by line by the human submitter.