ci-tools: use bin instead of test-bin for non-test jobs#75851
Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom Mar 10, 2026
Merged
Conversation
The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor
The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor
Contributor
Author
|
/pj-rehearse |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-unit |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-frontend-checks |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-e2e-oo |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-breaking-changes pull-ci-openshift-ci-tools-main-e2e pull-ci-openshift-ci-tools-main-e2e-oo |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-frontend-checks |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-integration pull-ci-openshift-ci-tools-main-checkconfig |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-frontend-checks |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-ci-tools-main-integration pull-ci-openshift-ci-tools-main-checkconfig pull-ci-openshift-ci-tools-main-breaking-changes pull-ci-openshift-ci-tools-main-unit |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
|
@joepvd: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Contributor
Author
|
/pj-rehearse ack |
Contributor
|
@joepvd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
Contributor
|
/lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danilo-gemoli, joepvd The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
openshift-merge-bot
bot
merged commit 94252fc
into
openshift:main
17 of 18 checks passed
mpkredhat
pushed a commit
to mpkredhat/release
that referenced
this pull request
Mar 11, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
kasturinarra
pushed a commit
to kasturinarra/release
that referenced
this pull request
Mar 11, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
ibm-adarsh
pushed a commit
to ibm-adarsh/release
that referenced
this pull request
Mar 12, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
amp-rh
pushed a commit
to amp-rh/openshift-release
that referenced
this pull request
Mar 12, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
tareqalayan
pushed a commit
to tareqalayan/release
that referenced
this pull request
Mar 13, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
qiliRedHat
pushed a commit
to qiliRedHat/release
that referenced
this pull request
Mar 13, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
MayXuQQ
pushed a commit
to MayXuQQ/release
that referenced
this pull request
Mar 17, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
kasturinarra
pushed a commit
to kasturinarra/release
that referenced
this pull request
Mar 17, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
sairameshv
pushed a commit
to sairameshv/release
that referenced
this pull request
Mar 23, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
zhouying7780
pushed a commit
to zhouying7780/release
that referenced
this pull request
Mar 25, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 25, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
anpingli
pushed a commit
to anpingli/release
that referenced
this pull request
Mar 30, 2026
) * ci-tools: use bin instead of test-bin for non-test jobs The integration, breaking-changes, checkconfig, and frontend-checks jobs were using `from: test-bin`, which triggers `make race-install` (~28 min) to compile all binaries with the race detector. These jobs only run CLI tools for deterministic operations on local files and do not benefit from race instrumentation. Switch them to `from: bin` so they reuse the production binaries already built by the images job via `make production-install`, avoiding a redundant expensive compilation step. Made-with: Cursor * ci-tools: bump unit test resources for race detector The unit test runs `go test -race -count=25 ./...` which needs significantly more memory and CPU than the 1Gi/1CPU default. Race-instrumented tests typically use 5-10x more memory. Bump to 4Gi memory and 4 CPU to reduce GC pressure and allow better parallelism. Made-with: Cursor * ci-tools: use src for frontend-checks instead of bin The bin image removes frontend/dist/dummy files during make production-install, causing verify-frontend-format to detect a git diff and fail. frontend-checks only runs npm/prettier checks and does not need compiled Go binaries. Made-with: Cursor * ci-tools: restore dummy files before frontend-checks on bin image The bin image removes frontend/dist/dummy files during make production-install. Restore them before running verify-frontend-format to prevent a spurious git diff failure. This lets frontend-checks use from: bin (with pre-built node_modules) instead of from: src (which requires a slow npm ci install). Made-with: Cursor
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
3 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.
Summary
integration,breaking-changes,checkconfig, andfrontend-checksjobs fromfrom: test-bintofrom: binin the ci-operator config foropenshift/ci-tools.test-bintriggersmake race-install(~28 min), adding an unnecessary expensive compilation step.from: bin, these jobs reuse the production binaries already built by theimagesjob (make production-install), leveraging ci-operator's namespace-level image caching to skip compilation entirely when thebinimage already exists.unitjob, as the compilation and run ofgo -raceis memory and cpu intensive.Impact
Expected CI time savings of ~28 minutes per affected job invocation (4 jobs), as each no longer needs to independently compile all binaries with
-race. Expected speed up ofunitjob.