Kokoro: Don't use verbose logging for make

When the build fails, it's very hard to find the compiler error in the spam. Change-Id: Ic975f0a075e4104db82a58ef03e1ba643e520fe2 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/26031 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by: Ben Clayton <bclayton@google.com> Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Kokoro: Don't use verbose logging for make
4c84dbdc · Ben Clayton · e57f10e4 · 4c84dbdc
Commit 4c84dbdc authored Mar 02, 2019 by Ben Clayton
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 1 deletion

continuous.sh kokoro/gcp_ubuntu/continuous.sh +2 -1

No files found.
--- a/kokoro/gcp_ubuntu/continuous.sh
+++ b/kokoro/gcp_ubuntu/continuous.sh
@@ -12,7 +12,7 @@ git submodule update --init
 mkdir -p build && cd build

 cmake ..
-make --jobs=$(nproc) VERBOSE=1
+make --jobs=$(nproc)

 # Run the GLES unit tests.
 ./unittests
\ No newline at end of file