aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts
diff options
context:
space:
mode:
authorGravatar Klaus Aehlig <aehlig@google.com>2017-11-21 08:22:32 -0800
committerGravatar Copybara-Service <copybara-piper@google.com>2017-11-21 08:25:57 -0800
commit7f72af113960386006598150e880a79b5f0bc2e1 (patch)
treee0f3415c37474ebab8783cdd74ebac75348ec6de /scripts
parentedc3901ecaafdb778a8e9fac463af1b2812f8f48 (diff)
Fix //src/test/shell/integration:progress_reporting_test
The test case test_failed_actions_with_keep_going was never correct and only worked by accident: it relied on bazel starting at least two actions, if for there are at least two where all the dependencies are already met; however bazel is clever and analyzes the resources of the system it is running in, and if they are small will only run one genrule at a time. Fix this by telling it to run 2 actions and lying about the available resources of the local system. Also increase the test size and reenable the test for remote execution. Fixes #3995. Change-Id: Ic84de17a98a2e74c24901d4efb38d7631de4690a PiperOrigin-RevId: 176511026
Diffstat (limited to 'scripts')
-rw-r--r--scripts/ci/bazel-tests-remote.json2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/ci/bazel-tests-remote.json b/scripts/ci/bazel-tests-remote.json
index 00f376756f..6123068428 100644
--- a/scripts/ci/bazel-tests-remote.json
+++ b/scripts/ci/bazel-tests-remote.json
@@ -26,7 +26,7 @@
"--java_toolchain=@bazel_toolchains//configs/java/0.1.0/bazel_0.6.0:remote_toolchain"
],
"tests": [
- "tests(//src/test/shell/integration/...) - //src/test/shell/integration:progress_reporting_test",
+ "//src/test/shell/integration/...",
"//src/test/java/... - //src/test/java/com/google/devtools/build/android/..."
],
"test_tag_filters": ["-slow"],