tooling: run the conformance suite without Docker#192
Merged
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
This was referenced Jun 12, 2026
The Docker path needs the private GHCR tools image (or a local image build) plus a Docker daemon — unavailable in some dev environments. conformance_test_runner drives the testee over stdin/stdout pipes, so nothing actually requires a container: - scripts/build-conformance-tools.sh (task conformance-tools-local): native equivalent of Dockerfile.tools — pre-installs jsoncpp, builds conformance_test_runner from the pinned protobuf tag into .local/bin/ (host-linked; the image's -static is only needed for distribution), and populates conformance/protos/ with the same proto set. - scripts/run-conformance-local.sh (task conformance-local): native equivalent of run-conformance.sh + the image build — cargo-builds the std/no_std conformance binaries and executes the same seven runs (including via-lazy) with the same failure lists and CONFORMANCE_OUT logging.
iainmcgin
force-pushed
the
tooling/conformance-local
branch
from
84fe4e7 to
1d9e840
Compare
kollektiv
approved these changes
Jun 16, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
What this does
Adds a Docker-free path for running the protobuf conformance suite. The Docker path needs the GHCR tools image (or a local image build) plus a daemon, which some dev environments don't have.
conformance_test_runnerdrives the testee over stdin/stdout pipes, so nothing actually requires a container.scripts/build-conformance-tools.sh(task conformance-tools-local): native equivalent ofDockerfile.tools— buildsconformance_test_runnerfrom the pinned protobuf tag into.local/bin/and populatesconformance/protos/with the same proto set. One-time, ~10–20 min.scripts/run-conformance-local.sh(task conformance-local): native equivalent ofrun-conformance.sh— cargo-builds the std/no_std conformance binaries and executes the same seven runs (std, no_std, via-view, via-lazy, view-json, via-reflect, via-vtable) with the same failure lists andCONFORMANCE_OUTlogging.No runtime or codegen changes; CONTRIBUTING gains a "Without Docker" section.
Why now
This is the verification rig for the upcoming 0.8.0 generated-code-readability PRs — it lets each one be conformance-checked in environments without Docker, instead of relying solely on the CI conformance job.
How we know it works
task conformance-tools-localbuilds the runner cleanly from source; the full seven-run suite was executed against main + the first readability PR via these scripts (logs captured withCONFORMANCE_OUT). markdownlint clean on the CONTRIBUTING change.