-
Notifications
You must be signed in to change notification settings - Fork 27.7k
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
Retry connecting to device in CI after lost connection #133769
Retry connecting to device in CI after lost connection #133769
Conversation
Google testing seems to be failing on something unrelated. I tried clicking "Re-run" but hasn't done anything yet. I'll give it a little time and if not, I'll update the branch to trigger it to rerun. |
portForwarder: isWirelesslyConnected ? null : portForwarder, | ||
hostPort: debuggingOptions.hostVmServicePort, | ||
devicePort: debuggingOptions.deviceVmServicePort, | ||
vmServiceDiscovery = _setupDebuggerAndVmServiceDiscovery( |
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.
from a cursory look, this diff doesn't change anything, just factors out the left side logic to a helper method, is that right?
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.
Pretty much, only difference is I added a skipInstall
option
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.
LGTM
BTW, your google testing failure looks like a bug with FRoB. I chatted with the release team who is on it, I think they are going to put out a PSA soon. |
Thanks for the heads up! |
Sometimes
ios-deploy
loses connection to the device after installing, starting debugserver, and launching. This is shown with an error message like:This happens frequently in our CI system: #120808
Usually in CI, on retry it'll work and pass - so this is an attempt to retry without failing the test first. It's not guaranteed to fix since we're unable to recreate this error locally.
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.