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: adb forked server process is kept alive after tests #4853
Comments
|
@jin Is this still an issue? What causes an adb server to become forked? |
I haven't seen this issue occur personally for a while, but I know some users, both internal and external, have seen it recently. My hunch is that the emulator launcher is not properly killing the servers after shutting down, but I haven't looked into that further. |
Downgrading to P4 as there's a new emulator launcher in the works. |
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 3 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 ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team ( |
When an
android_instrumentation_test
completes, the forkedadb
servers are not cleaned up and it leads to this:The text was updated successfully, but these errors were encountered: