kokoro: Avoid using Kokoro's env_vars setting

It makes it hard to run ephemeral jobs, and we don't actually need it
here because we aren't changing the setting with manual runs.
This commit is contained in:
Eric Anderson 2024-02-09 10:45:33 -08:00
parent 6847219657
commit d568a8dc19
2 changed files with 5 additions and 8 deletions

View File

@ -4,14 +4,6 @@
build_file: "grpc-java/buildscripts/kokoro/macos.sh"
timeout_mins: 45
# We had problems with random tests timing out because it took seconds to do
# trivial (ns) operations. The Mac machines have 2 cores with 4 logical
# threads, so Gradle should be using 4 workers by default.
env_vars {
key: "GRADLE_FLAGS"
value: "--max-workers=2"
}
# We always build mvn artifacts.
action {
define_artifacts {

View File

@ -7,6 +7,11 @@ fi
readonly GRPC_JAVA_DIR="$(cd "$(dirname "$0")"/../.. && pwd)"
# We had problems with random tests timing out because it took seconds to do
# trivial (ns) operations. The Kokoro Mac machines have 2 cores with 4 logical
# threads, so Gradle should be using 4 workers by default.
export GRADLE_FLAGS="${GRADLE_FLAGS:-} --max-workers=2"
. "$GRPC_JAVA_DIR"/buildscripts/kokoro/kokoro.sh
trap spongify_logs EXIT