You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unit tests and golangci-lint are taking a long time to run in Prow
environments, sometimes timing out and causing CI flakes. Likely, this
is a result of the CI detecting the number of CPUs on the host, yet
being limited to fewer CPUs (2 currently) in the Prow job config.
Regardless of whether Prow jobs are updated to allow more CPU/memory
usage, it is still important to be able to limit concurrency to what is
configured in the job to avoid the issue if Prow machines become
significantly bigger in the future.
Prow jobs will need to be updated to make use of these new scripts.
Signed-off-by: Blaine Gardner <[email protected]>
Copy file name to clipboardExpand all lines: Makefile
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -89,12 +89,12 @@ test-e2e: chainsaw # Run e2e tests against the K8s cluster specified in ~/.kube/
89
89
.PHONY: lint
90
90
lint: golangci-lint.client golangci-lint.controller golangci-lint.sidecar ## Run all linters (suggest `make -k`)
91
91
golangci-lint.%: golangci-lint
92
-
cd$*&&$(GOLANGCI_LINT) run --config $(CURDIR)/.golangci.yaml --new
92
+
cd$*&&$(GOLANGCI_LINT) run $(GOLANGCI_LINT_RUN_OPTS)--config $(CURDIR)/.golangci.yaml --new
93
93
94
94
.PHONY: lint-fix
95
95
lint-fix: golangci-lint-fix.client golangci-lint-fix.controller golangci-lint-fix.sidecar ## Run all linters and perform fixes where possible (suggest `make -k`)
96
96
golangci-lint-fix.%: golangci-lint
97
-
cd$*&&$(GOLANGCI_LINT) run --config $(CURDIR)/.golangci.yaml --new --fix
97
+
cd$*&&$(GOLANGCI_LINT) run $(GOLANGCI_LINT_RUN_OPTS)--config $(CURDIR)/.golangci.yaml --new --fix
0 commit comments