prow: debug GOMAXPROCS instead of setting it

GOMAXPROCS is now being set in the prow job config. However, the issue
of unit tests and lint runs being throttled could still be a risk.
Instead of setting a hardcoded GOMAXPROCS value, log the value in the
test/lint runs so we can debug any potential issues in the future.

Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>

Author: BlaineEXE

hack/prow-lint.sh

@@ -3,9 +3,11 @@ set -o errexit
 set -o nounset
 set -o xtrace
 
+echo "GOMAXPROCS: $GOMAXPROCS" # debug prow CPU limit to ensure job not being throttled
+
 GOLANGCI_LINT_RUN_OPTS=""
 GOLANGCI_LINT_RUN_OPTS="$GOLANGCI_LINT_RUN_OPTS --verbose" # debug linter timing and mem usage
-GOLANGCI_LINT_RUN_OPTS="$GOLANGCI_LINT_RUN_OPTS --concurrency=2" # prow job lags if too many threads
+GOLANGCI_LINT_RUN_OPTS="$GOLANGCI_LINT_RUN_OPTS --concurrency=$GOMAXPROCS" # golangci-lint seems to do a bad job obeying GOMAXPROCS
 export GOLANGCI_LINT_RUN_OPTS
 
 make lint

hack/prow-test.sh

@@ -3,6 +3,6 @@ set -o errexit
 set -o nounset
 set -o xtrace
 
-export GOMAXPROCS=2 # prow job lags if too many threads
+echo "GOMAXPROCS: $GOMAXPROCS" # debug prow CPU limit to ensure job not being throttled
 
 make test