//src/test/shell/bazel/android/... is incompatible with RBE #8235

jin · 2019-05-03T20:51:50Z

Sample error:

Exception in thread "main" com.android.ide.common.internal.LoggedErrorException: Failed to run command:
	bazel-out/host/bin/external/androidsdk/aapt_binary package -f --no-crunch --no-version-vectors -I external/androidsdk/platforms/android-28/android.jar -M /tmp/resource_validator_tmp12788981107769083666/manifest-aapt-dummy/AndroidManifest.xml -m -J /tmp/resource_validator_tmp12788981107769083666/generated_resources --output-text-symbols /tmp/resource_validator_tmp12788981107769083666/generated_resources -F bazel-out/android-armeabi-v7a-fastbuild/bin/java/bazel/aar_files/library.ap_ --debug-mode --non-constant-id -0 apk
Error Code:
	127
Output:
	error parsing linebazel-out/host/bin/external/androidsdk/aapt_binary.runfiles/androidsdk/build-tools/28.0.3/aapt: error while loading shared libraries: libc++.so: cannot open shared object file: No such file or directory
	at com.google.devtools.build.android.AndroidResourceProcessor.runAapt(AndroidResourceProcessor.java:422)
	at com.google.devtools.build.android.AndroidResourceValidatorAction.main(AndroidResourceValidatorAction.java:148)
	at com.google.devtools.build.android.ResourceProcessorBusyBox$Tool$2.call(ResourceProcessorBusyBox.java:72)
	at com.google.devtools.build.android.ResourceProcessorBusyBox.processRequest(ResourceProcessorBusyBox.java:240)
	at com.google.devtools.build.android.ResourceProcessorBusyBox.main(ResourceProcessorBusyBox.java:203)

Key problem: error parsing linebazel-out/host/bin/external/androidsdk/aapt_binary.runfiles/androidsdk/build-tools/28.0.3/aapt: error while loading shared libraries: libc++.so: cannot open shared object file: No such file or directory

It looks the dynamically linked libc++.so dependency of aapt/aapt2 at sdk/build-tools/<version>/lib64/libc++.so cannot be found when executing Android actions remotely through a Bazel-in-Bazel sh_test. This suggests some kind of issue with the hermeticity of @androidsdk//:aapt_binary and @androidsdk//:aapt2_binary.

Regular Android builds do work with RBE, however.

cc @buchgr

trunk issue: #8033

The text was updated successfully, but these errors were encountered:

buchgr · 2019-05-06T12:35:02Z

Related #4663

don't run them on remote execution until #8235 is fixed. They will continue to run locally. RELNOTES: None PiperOrigin-RevId: 246863889

buchgr · 2019-05-07T08:43:17Z

We have tagged the android shell tests as "no-remote" for now.

Fixes bazelbuild#8235.

The dynamic linking issue that required local execution has been fixed. This should speed up Bazel CI runs, as we previously couldn't benefit from previously cached test results. One of the tests must remain non-remote because it currently exceeds the RBE input limit (70k files). This is tracked in bazelbuild#17784. Fixes bazelbuild#8235.

…les used by the Android integration tests. This is necessary to reenable remote caching/execution for these tests (and make CI runs faster!). In the absence of this change, the tests will fail because the aapt/appt2/aidl/zipalign tools can't be dynamically linked in the remote environment. See issue #8235. We need to wait until this change makes it into a Bazel release before reenabling the tests, as they inherit the SDK files from the Bazel that runs them. Related to #8235. PiperOrigin-RevId: 517180365 Change-Id: I2baa66af15af85349187e75e3acd4e3cb5d84a49

…f SDK files used by the Android integration tests. This is necessary to reenable remote caching/execution for these tests (and make CI runs faster!). In the absence of this change, the tests will fail because the aapt/appt2/aidl/zipalign tools can't be dynamically linked in the remote environment. See issue bazelbuild#8235. We need to wait until this change makes it into a Bazel release before reenabling the tests, as they inherit the SDK files from the Bazel that runs them. Related to bazelbuild#8235. PiperOrigin-RevId: 517180365 Change-Id: I2baa66af15af85349187e75e3acd4e3cb5d84a49

…f SDK files used by the Android integration tests. (#17826) This is necessary to reenable remote caching/execution for these tests (and make CI runs faster!). In the absence of this change, the tests will fail because the aapt/appt2/aidl/zipalign tools can't be dynamically linked in the remote environment. See issue #8235. We need to wait until this change makes it into a Bazel release before reenabling the tests, as they inherit the SDK files from the Bazel that runs them. Related to #8235. PiperOrigin-RevId: 517180365 Change-Id: I2baa66af15af85349187e75e3acd4e3cb5d84a49

github-actions · 2023-04-13T01:31:33Z

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 2+ 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.

tjgq · 2023-04-13T09:09:30Z

This issue was fixed by #17826 but we need to wait until it makes it into a Bazel release before we can reenable the tests (except android_ndk_integration_test, which requires additional work to address #17784).

Fixes bazelbuild#8235.

… tests. Some still fail remotely and remain disabled; see bazelbuild#17784 and bazelbuild#18431. Fixes bazelbuild#8235.

…les used by the Android integration tests. This is necessary to reenable remote caching/execution for these tests (and make CI runs faster!). In the absence of this change, the tests will fail because the aapt/appt2/aidl/zipalign tools can't be dynamically linked in the remote environment. See issue bazelbuild#8235. We need to wait until this change makes it into a Bazel release before reenabling the tests, as they inherit the SDK files from the Bazel that runs them. Related to bazelbuild#8235. PiperOrigin-RevId: 517180365 Change-Id: I2baa66af15af85349187e75e3acd4e3cb5d84a49

… tests. Some still fail remotely and remain disabled; see bazelbuild#17784 and bazelbuild#18431. Fixes bazelbuild#8235. Closes bazelbuild#18387. PiperOrigin-RevId: 533332908 Change-Id: I638420de72ca1efdb1b79fa1c1fec68d3a740eb5

meteorcloudy · 2024-02-21T16:07:04Z

@tjgq Can we remove no-remote for those tests now? a9fb6d3

tjgq · 2024-02-21T16:14:42Z

I don't know, but we could give it a try and see if we're still hitting the same error.

jin added team-Android Issues for Android team untriaged labels May 3, 2019

bazel-io pushed a commit that referenced this issue May 6, 2019

tag //src/test/shell/bazel/android/... test as 'no-remote'

d466182

don't run them on remote execution until #8235 is fixed. They will continue to run locally. RELNOTES: None PiperOrigin-RevId: 246863889

buchgr mentioned this issue May 7, 2019

Fix remote tests to work on RBE #8033

Open

26 tasks

ahumesky added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels May 14, 2019

ahumesky added the type: bug label Dec 3, 2020

meteorcloudy mentioned this issue Oct 20, 2022

Integration tests are not cached in presubmit on trivial change #16518

Open

tjgq mentioned this issue Mar 15, 2023

Run the Android integration tests remotely again. #17783

Closed

tjgq added a commit to tjgq/bazel that referenced this issue Mar 15, 2023

Run the Android integration tests remotely again.

0ca42ee

Fixes bazelbuild#8235.

tjgq added a commit to tjgq/bazel that referenced this issue Mar 15, 2023

Run the Android integration tests remotely again.

cb198d6

Fixes bazelbuild#8235.

tjgq mentioned this issue Mar 15, 2023

android_ndk_integration_test exceeds 70k input limit for RBE #17784

Open

tjgq mentioned this issue Mar 20, 2023

[6.2.0] Include build-tools/X.Y.Z/{lib,lib64}/** in the minimal set of SDK files used by the Android integration tests. #17826

Merged

github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Apr 13, 2023

github-actions bot removed the stale Issues or PRs that are stale (no activity for 30 days) label Apr 14, 2023

tjgq added a commit to tjgq/bazel that referenced this issue May 12, 2023

Reenable remote caching/execution for Android integration tests.

0e6c625

Fixes bazelbuild#8235.

tjgq mentioned this issue May 12, 2023

Reenable remote caching/execution for most of the Android integration tests. #18387

Closed

tjgq added a commit to tjgq/bazel that referenced this issue May 15, 2023

Reenable remote caching/execution for Android integration tests.

114e976

Fixes bazelbuild#8235.

tjgq added a commit to tjgq/bazel that referenced this issue May 17, 2023

Reenable remote caching/execution for most of the Android integration…

29211e7

… tests. Some still fail remotely and remain disabled; see bazelbuild#17784 and bazelbuild#18431. Fixes bazelbuild#8235.

tjgq added a commit to tjgq/bazel that referenced this issue May 17, 2023

Reenable remote caching/execution for most of the Android integration…

a0c05a9

… tests. Some still fail remotely and remain disabled; see bazelbuild#17784 and bazelbuild#18431. Fixes bazelbuild#8235.

copybara-service bot closed this as completed in a9fb6d3 May 19, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

//src/test/shell/bazel/android/... is incompatible with RBE #8235

//src/test/shell/bazel/android/... is incompatible with RBE #8235

jin commented May 3, 2019 •

edited

Loading

buchgr commented May 6, 2019

buchgr commented May 7, 2019

github-actions bot commented Apr 13, 2023

tjgq commented Apr 13, 2023

meteorcloudy commented Feb 21, 2024

tjgq commented Feb 21, 2024

//src/test/shell/bazel/android/... is incompatible with RBE #8235

//src/test/shell/bazel/android/... is incompatible with RBE #8235

Comments

jin commented May 3, 2019 • edited Loading

buchgr commented May 6, 2019

buchgr commented May 7, 2019

github-actions bot commented Apr 13, 2023

tjgq commented Apr 13, 2023

meteorcloudy commented Feb 21, 2024

tjgq commented Feb 21, 2024

jin commented May 3, 2019 •

edited

Loading