SHAFT_ENGINE: [Bug]: Adjust "attemptRemoteServerPing" to check status without "/" or adding flag to disable this check
Problem:
To run against remote execution, SHAFT first make ping request to the server to check its status using status/ or wd/hub/status/,
some servers response with 404 although it is up and running that’s happen as the status call ends with / and some servers doesn’t support it. They support status call without / at the end.
Reference code is here
Suggestions:
- Add another call to
statuswithout/in case 404 returned from first request - Add flag to disable this check if needed
Note: This issue blocks the tests execution on some servers
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 16 (7 by maintainers)
Commits related to this issue
- Fix for #963 by adding the flag — committed to magdyheiba/SHAFT_ENGINE by magdyheiba a year ago
- Fix Bug#963 and adding Flags interface (#980) * Fix Bug #960 and enhance overlay images * Removing the IF else conditions * Adding the remote overlay image path and fix the width and height iss... — committed to ShaftHQ/SHAFT_ENGINE by magdyheiba a year ago
- parameterize remote server connection timeouts - add new timeouts and disable connection establishment by default - update timeouts in the configuration manager - update timeouts properties files - u... — committed to ShaftHQ/SHAFT_ENGINE by MohabMohie a year ago
Issue is fixed, there was conflict in the dependencies