chore(seed): remove stale go-sdk exhaustive:omit-empty-request-wrappers allowedFailure#16298
chore(seed): remove stale go-sdk exhaustive:omit-empty-request-wrappers allowedFailure#16298iamnamananand996 wants to merge 1 commit into
Conversation
…rs allowedFailure The exhaustive:omit-empty-request-wrappers fixture passes its wire tests in isolation (verified across multiple local runs). It only appeared to fail when run alongside exhaustive:no-custom-config locally, because both configs reuse the same WireMock container name (wiremock-exhaustive-wiremock-1) and collide. In CI the two configs run in separate matrix jobs, so there is no collision and the fixture passes. No generator change is required.
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
SDK Generation Benchmark ResultsComparing PR branch against median of 5 nightly run(s) on Full benchmark table (click to expand)
main (generator): generator-only time via --skip-scripts (includes Docker image build, container startup, IR parsing, and code generation — this is the same Docker-based flow customers use via |
Description
Part of the one-by-one effort to clear go-sdk
allowedFailures.exhaustive:omit-empty-request-wrappersis a stale allowed failure — it passes. It only appeared to fail in local seed runs because of a Docker container-name collision, not a generator bug.Root cause: both
exhaustiveconfigs (no-custom-configandomit-empty-request-wrappers) spin up a WireMock container namedwiremock-exhaustive-wiremock-1(derived from the fixture nameexhaustive). When the two configs run concurrently in a single localseed testinvocation, the seconddocker compose upfails with:Whichever config wins the race runs its wire tests for ~40s and passes; the loser fails fast (~1s). In CI the two configs run in separate matrix jobs, so there is no collision and both pass.
Changes Made
exhaustive:omit-empty-request-wrappersfromallowedFailuresinseed/go-sdk/seed.yml.Testing
--outputFolder omit-empty-request-wrappers) 3x — passes every time (wire tests ~40s). Seed CLI reports: "1/1 test cases succeeded unexpectedly. Consider removing the following fixtures from allowedFailures: exhaustive:omit-empty-request-wrappers."seed-test-results (go-sdk)to confirm green with the entry removed.Link to Devin session: https://app.devin.ai/sessions/6ba63e4405694aa8ab8875f0dbfd9afc
Requested by: @iamnamananand996