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_ndk_integration_test exceeds 70k input limit for RBE #17784

Open
tjgq opened this issue Mar 15, 2023 · 1 comment
Open

android_ndk_integration_test exceeds 70k input limit for RBE #17784

tjgq opened this issue Mar 15, 2023 · 1 comment
Labels
stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team

Comments

@tjgq
Copy link
Contributor

tjgq commented Mar 15, 2023

I found this while attempting to re-enable remote execution for the Android integration tests (#8235).

ERROR: /workdir/src/test/shell/bazel/android/BUILD:113:16: Testing //src/test/shell/bazel/android:android_ndk_integration_test_with_platforms (shard 3 of 6) failed: (Exit 34): INVALID_ARGUMENT: Input tree has 75575 files, above the maximum of 70000

We should try to trim down the inputs or, failing that, try to get the limit raised. The inability to run remotely impacts Bazel CI latency, since we can never reuse a cached result.

@tjgq tjgq added the team-Android Issues for Android team label Mar 15, 2023
tjgq added a commit to tjgq/bazel that referenced this issue Mar 15, 2023
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.
tjgq added a commit to tjgq/bazel that referenced this issue May 17, 2023
tjgq added a commit to tjgq/bazel that referenced this issue May 17, 2023
copybara-service bot pushed a commit that referenced this issue May 19, 2023
… tests.

Some still fail remotely and remain disabled; see #17784 and #18431.

Fixes #8235.

Closes #18387.

PiperOrigin-RevId: 533332908
Change-Id: I638420de72ca1efdb1b79fa1c1fec68d3a740eb5
fweikert pushed a commit to fweikert/bazel that referenced this issue May 25, 2023
… 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
Copy link

github-actions bot commented Sep 5, 2024

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 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team
Projects
None yet
Development

No branches or pull requests

2 participants
@tjgq and others