-
Notifications
You must be signed in to change notification settings - Fork 179
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
[WIP] Utilize tcp:0 to find available adb port instead of portpicker #871
[WIP] Utilize tcp:0 to find available adb port instead of portpicker #871
Conversation
Looks like this PR caused presubmit failed in cl/510984231. Taking a look tomorrow. Marking this as WIP for now. |
By default, the ADB binary supports this feature, i.e. it supports passing 0 | ||
as host port when doing port forwarding. | ||
|
||
But sometimes users override the `ADB` variable to use a customized variant to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we afford to wait for the migration to adb forwarder to push this PR, or is there some urgency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not urgent, we can wait for the migration.
Are we ready to submit this now? |
Currently waterfall migration is not completed, waiting until the end of this year, if it is still not completed I will submit the PR. |
Now we can do this with simpler code. Closing this and created a new PR #904 |
When using adb, we can utilize tcp:0 to find available adb port instead of portpicker.
However, when using other ADB alternatives (i.e. waterfall), portpicker is still used, because waterfall forward doesn't print out which port it picked.
This change is