-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
android_instrumentation_test test project failing in sandbox on Bazel CI #4979
Comments
It's passing now: https://buildkite.com/bazel/android-testing/builds/5 |
Looks like we're getting non-deterministic failures with the Maven downloads:
https://buildkite.com/bazel/android-testing/builds/7#bc05d42f-5b5c-45c0-ada4-4ec88d3cb5d0 |
We're getting timeout failures for tests on API 19, 21 and 22. 14.04: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/217#5c8577e8-7207-45af-96ec-cb7fc7170f92 |
Blocked on issues in bazelbuild/bazel#4979
Blocked on issues in bazelbuild/bazel#4979
Removed tests for 19, 21 and 22. It's now green again. |
Blocked on issues in bazelbuild/bazel#4979
Blocked on issues in bazelbuild/bazel#4979
This is the tracking bug for making the canonical googlesamples/android-testing project pass on Bazel CI postsubmit. Setup instructions available here: https://gist.github.com/jin/6babcbe600d8ee24c732494118f4bb27
This is not a release blocker for 0.12.0.
Latest run: https://buildkite.com/bazel/android-testing/builds/2
Issues:
--spawn_strategy=local
workaround required due to Xvfb lockfile bug. internal ref b/72871646 / blocked on on Update ATSL commit to include the fix for sandboxed tests android/testing-samples#184The text was updated successfully, but these errors were encountered: