Repository navigation
Make integration-test parallelism configurable via GINKGO_NODES - #1173
Merged
Merged
Conversation
The integration suite hardcoded nodes=3 (GOMAXPROCS bounding spec.Parallel()) and ignored the GINKGO_NODES env var that the buildpacks-ci pipeline already passes to the run-buildpack-integration-specs task. As a result, tuning GINKGO_NODES in the pipeline had no effect on the integration specs. Honour GINKGO_NODES (default 3, preserving current behavior) so the pipeline can lower parallelism on the single-AZ test CF, where heavy Rails fixtures otherwise saturate the single Diego cell and cause transient gorouter 404s and staging timeouts.
tnikolova82
approved these changes
Oct 2, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The integration suite hardcoded nodes=3 (GOMAXPROCS bounding spec.Parallel()) and ignored the GINKGO_NODES env var that the buildpacks-ci pipeline already passes to the run-buildpack-integration-specs task. As a result, tuning GINKGO_NODES in the pipeline had no effect on the integration specs.
Honour GINKGO_NODES (default 3, preserving current behavior) so the pipeline can lower parallelism on the single-AZ test CF, where heavy Rails fixtures otherwise saturate the single Diego cell and cause transient gorouter 404s and staging timeouts.
Connected with Stabilize ruby-buildpack integration tests against single-AZ resource contention- #680