Skip to content
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

Closed
4 of 5 tasks
jin opened this issue Apr 9, 2018 · 5 comments
Closed
4 of 5 tasks
Assignees
Labels
P1 I'll work on this now. (Assignee required) type: bug

Comments

@jin
Copy link
Member

jin commented Apr 9, 2018

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:

@jin jin added type: bug P1 I'll work on this now. (Assignee required) category: rules > android labels Apr 9, 2018
@jin jin self-assigned this Apr 9, 2018
@jin
Copy link
Member Author

jin commented Apr 9, 2018

cc @slinzner @ahumesky

@jin
Copy link
Member Author

jin commented Apr 12, 2018

@jin jin changed the title android_instrumentation_test test project failing on Bazel CI android_instrumentation_test test project failing in sandbox on Bazel CI Apr 12, 2018
@jin
Copy link
Member Author

jin commented Apr 13, 2018

Looks like we're getting non-deterministic failures with the Maven downloads:

[INFO] ------------------------------------------------------------------------
--
  | [INFO] BUILD FAILURE
  | [INFO] ------------------------------------------------------------------------
  | [INFO] Total time: 5.795s
  | [INFO] Finished at: Fri Apr 13 06:30:02 UTC 2018
  | [INFO] Final Memory: 13M/1811M
  | [INFO] ------------------------------------------------------------------------
  | [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get (default-cli) on project standalone-pom: Execution default-cli of goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get failed: Plugin org.apache.maven.plugins:maven-dependency-plugin:2.10 or one of its dependencies could not be resolved: The following artifacts could not be resolved: backport-util-concurrent:backport-util-concurrent:jar:3.1, org.apache.maven.reporting:maven-reporting-impl:jar:2.2: Could not find artifact backport-util-concurrent:backport-util-concurrent:jar:3.1 -> [Help 1]
  | [ERROR]
  | [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
  | [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  | [ERROR]
  | [ERROR] For more information about the errors and possible solutions, please read the following articles:
  | [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
  |  
  | + mvn -s settings.xml org.apache.maven.plugins:maven-dependency-plugin:2.10:get -Dtransitive=false -Dartifact=com.android.support:support-compat:27.0.2:aar
  |  
  | Failed to fetch Maven dependency and referenced by '@com_android_support_support_vector_drawable_27_0_2//aar:aar'
  | ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/1e68441e02182c8fbba725ba9b4d7033/external/com_android_support_support_media_compat_27_0_2/aar/BUILD:4:1: no such package '@com_android_support_support_compat_27_0_2//aar': Traceback (most recent call last):
  | File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/1e68441e02182c8fbba725ba9b4d7033/external/bazel_tools/tools/build_defs/repo/maven_rules.bzl", line 292
  | _maven_artifact_impl(ctx, "aar", _maven_aar_build_file_te...)
  | File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/1e68441e02182c8fbba725ba9b4d7033/external/bazel_tools/tools/build_defs/repo/maven_rules.bzl", line 258, in _maven_artifact_impl
  | _mvn_download(ctx = ctx, paths = paths, fully_qual...)
  | File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/1e68441e02182c8fbba725ba9b4d7033/external/bazel_tools/tools/build_defs/repo/maven_rules.bzl", line 211, in _mvn_download
  | fail(("%s\n%s\nFailed to fetch Maven ...)))
[INFO] ------------------------------------------------------------------------
  | [INFO] BUILD FAILURE
  | [INFO] ------------------------------------------------------------------------
  | [INFO] Total time: 5.109s
  | [INFO] Finished at: Fri Apr 13 06:33:48 UTC 2018
  | [INFO] Final Memory: 13M/1811M
  | [INFO] ------------------------------------------------------------------------
  | [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get (default-cli) on project standalone-pom: Execution default-cli of goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get failed: Plugin org.apache.maven.plugins:maven-dependency-plugin:2.10 or one of its dependencies could not be resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-dependency-plugin:jar:2.10 (): Failed to read artifact descriptor for org.apache.maven.shared:maven-shared-io:jar:1.1: Could not find artifact org.apache.maven.shared:maven-shared-components:pom:8 -> [Help 1]
  | [ERROR]
  | [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
  | [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  | [ERROR]
  | [ERROR] For more information about the errors and possible solutions, please read the following articles:
  | [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
  |  
  | + mvn -s settings.xml org.apache.maven.plugins:maven-dependency-plugin:2.10:get -Dtransitive=false -Dartifact=com.android.support.test.espresso:espresso-idling-resource:3.0.1:aar

Failed to fetch Maven dependency and referenced by '//ui/espresso/IdlingResourceSample:IdlingResourceSampleTestLib'

https://buildkite.com/bazel/android-testing/builds/7#bc05d42f-5b5c-45c0-ada4-4ec88d3cb5d0

jin added a commit to bazelbuild/continuous-integration that referenced this issue Apr 30, 2018
buchgr pushed a commit to bazelbuild/continuous-integration that referenced this issue May 4, 2018
@jin
Copy link
Member Author

jin commented Aug 1, 2018

Removed tests for 19, 21 and 22. It's now green again.

@jin jin closed this as completed Aug 1, 2018
buchgr pushed a commit to bazelbuild/continuous-integration that referenced this issue Sep 5, 2018
joeleba pushed a commit to joeleba/continuous-integration that referenced this issue Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 I'll work on this now. (Assignee required) type: bug
Projects
None yet
Development

No branches or pull requests

1 participant