-
Notifications
You must be signed in to change notification settings - Fork 8
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
implement wda/stf auto healing #151
Comments
done. during setup we configure custom LaunchAgent script per device which can run to kickoff recovery manually you can use such command
as result we try to start one more tme: wda, appium and stf. all launchagent actions are tracked in |
Test scenario for Simulator:
Expected result: Simulator restarted and available on STF Test scenario for iOS:
Actual result: iOS device is not up and running on STF. WorkAround: Logs:
|
closing again. right after setup we don't do start anymore.. so new scenario:
-> recovery script is activated (use |
Still repro after run:
NOTE: iOS device restarted and up and running on STF after 8-9min. Please see Logs 2 for this issue Logs:
Logs 2:
|
#151: added wda stop for recovery to make prot forwarding workable af…
added wda stop during recovery step. so this time we expect to restart wda, port forwarding for wda and mjpeg and stf. Appium is not restarted so exception to bind to appium port is ok during recovery. It is better to keep old appium to avoid all kind of selenium grid problems... |
Verified. |
we need stable solution to track state of the wda status. We already know that it might be done by connecting to mjpeg wda socket with
nc localhost port
.As only wda crashed connection is closed and we can do some actions asap. Amobg the actions we should do start of wda and stf.
Auto recovery should be done to support multiply recoveries after wda crashes.
The text was updated successfully, but these errors were encountered: