ci: use self-hosted httpbun in tests#2568
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Contributor
Code Coverage Report: Only Changed Files listed
Minimum allowed coverage is |
AlexV525
marked this pull request as ready for review
July 18, 2026 09:39
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.
Motivation
httpbun.comis currently returning HTTP 502 responses, which makes the integration tests fail independently of dio changes. The failure is visible in the PR #2567 stable job. CI already startshttpbun.local, but HTTP/2 pinning and all browser tests still used the public service.Changes
httpbun.comas the default outside the CI-local setup.onBadCertificateandvalidateCertificatereceive different certificates; that varies with the certificate chain and trust store.This touches TLS and certificate-pinning test infrastructure only; production TLS behavior is unchanged. Maintainers: please apply the extra scrutiny required for this sensitive area.
Verification
melos run formatandmelos run analyzepass. The local Chrome shared suite passes 54 tests with one existing skip against the HTTP container, including CORS, redirects, status codes, timeouts, and uploads. GitHub Actions passes on the minimum, stable, and beta SDK jobs, covering VM, Chrome, Firefox, and Flutter tests; the stable job also passes APK build and coverage generation.Implementation, tests, and local review by Codex.