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

Desugar opentelemetry-sdk-common for android failed #13472

Closed
hangqiu opened this issue May 13, 2021 · 3 comments
Closed

Desugar opentelemetry-sdk-common for android failed #13472

hangqiu opened this issue May 13, 2021 · 3 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: bug

Comments

@hangqiu
Copy link

hangqiu commented May 13, 2021

Description of the problem / feature request:

Using bazel to build android apps using the opentelemetry-api. Build failed with error below:

Desugaring v1/https/repo1.maven.org/maven2/io/opentelemetry/opentelemetry-sdk-common/1.2.0/opentelemetry-sdk-common-1.2.0.jar for Android failed: (Exit 1): desugar_java8 failed: error executing command bazel-out/k8-opt-exec-50AE0418/bin/external/bazel_tools/tools/android/desugar_java8 ... (remaining 1 argument(s) skipped)

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

relevant WORKSPACE file:

RULES_JVM_EXTERNAL_TAG = "4.0"

RULES_JVM_EXTERNAL_SHA = "31701ad93dbfe544d597dbe62c9a1fdd76d81d8a9150c2bf1ecf928ecdf97169"

http_archive(
name = "rules_jvm_external",
sha256 = RULES_JVM_EXTERNAL_SHA,
strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
url = "https://github.com/bazelbuild/rules_jvm_external/archive/%s.zip" % RULES_JVM_EXTERNAL_TAG,
)

load("@rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
artifacts = [
"io.opentelemetry:opentelemetry-api:1.+",
"io.opentelemetry:opentelemetry-context:1.+",
"io.opentelemetry:opentelemetry-sdk:1.+",
"io.opentelemetry:opentelemetry-sdk-common:1.+",
"io.opentelemetry:opentelemetry-sdk-trace:1.+",
"io.opentelemetry:opentelemetry-exporter-otlp:1.+",
"io.opentelemetry:opentelemetry-exporter-otlp-trace:1.+",
],
repositories = [
"https://maven.google.com",
"https://repo1.maven.org/maven2",
"https://jcenter.bintray.com",
],
)

relevant BUILD file
android_binary(
name = "blablabla",
srcs = glob([
"/*.java",
]),
assets = glob(["assets//"]),
assets_dir = "assets/",
custom_package = "blablabla.blablabla.blablabla",
manifest = "AndroidManifest.xml",
nocompress_extensions = ["tflite"],
resource_files = glob(["res/**/"]),
deps = [
"@maven//:io_opentelemetry_opentelemetry_sdk",
"@maven//:io_opentelemetry_opentelemetry_sdk_common",
"@maven//:io_opentelemetry_opentelemetry_sdk_trace",
"@maven//:io_opentelemetry_opentelemetry_exporter_otlp",
"@maven//:io_opentelemetry_opentelemetry_exporter_otlp_trace",
"@maven//:io_opentelemetry_opentelemetry_context",
"@maven//:io_opentelemetry_opentelemetry_api",
],
)

What operating system are you running Bazel on?

Compiler: android studio 4.2 RC1
OS: Ubuntu 18.04"

What's the output of bazel info release?

release 4.0.0

Have you found anything relevant by searching the web?

#11618
open-telemetry/opentelemetry-java#3231

From opentelemetry team: "sdk-common does have a multi-release jar, though. I wonder if bazel doesn't grok them?"

@aiuto aiuto added team-Android Issues for Android team untriaged labels May 14, 2021
@hangqiu
Copy link
Author

hangqiu commented May 18, 2021

Just wanna follow up on this. The android studio gradle works fine incorporating opentelemetry-sdk-common. But the bazel build doesn't work. Wondering if it has anything to do with the desugar.sh update

@ahumesky ahumesky added P2 We'll consider working on this in future. (Assignee optional) type: bug and removed untriaged labels Jun 18, 2021
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label May 10, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: bug
Projects
None yet
Development

No branches or pull requests

3 participants