mhardin
mhardin
Just curious if there are any updates on this? We are seeing the same issue in our test framework ('afterTest' hook gets skipped whenever a test times out). This is...
@adam-hampton-sp are you able to add unit tests around the new logic you added?
@ambirag looking at the code, AutomationStatusServlet:82 will only return a 400 if a run with UUID 'AutomationStatusServlet' already exists. I don't remember why that code was even added (to check...
@ambirag you should not be reusing the UUID when restarting runs. Since this is now a new run, it should have a new UUID (universally unique identifier). If you have...
@suveerprithipal I have seen this issue (I think it was introduced when the project was upgraded to Selenium 3.X) and it doesn't seem to cause any issues outside of not...
@suveerprithipal @RayChenLDL if a node is not connecting to the hub, possible causes could be the wrong IP address for the hub (for the node to connect to) was provided...
Interesting. Is it the hub or AWS terminating the nodes? The hub shouldn't terminate the node provided tests are running on them (you can check the grid console to see...
hi @khoshalarpy the log you gave me looks like Selenium's log. Can you provide me the grid scalers log? You can specify the log location (see readme) at process start...
Ah hah! So we have a task that basically goes and terminates "orphaned" nodes after a set period of time. Orphaned nodes are nodes that never connected to the hub...
@khoshalarpy I see 2 log snippets saying: `Nov 05, 2019 07:34:28:923 AM - ERROR [pool-5-thread-1] [AutomationRunContext] Node AutomationDynamicNode{uuid='AD-HOC', instanceId='i-077dc5d8e2db77d50', startDate=Tue Nov 05 07:14:14 GMT 2019, ipAddress='10.169.205.20'} was pending longer than...