Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Invalid
-
3.5.4
-
None
-
None
-
Windows - GitHub Actions
Description
Gremlin Server has been observed to occasionally slow down when running Integration and Cucumber Tests on Windows in GitHub Actions. Here is an example illustrating the slowdown:
Every so often (~2% of the time) on GitHub Actions, the Windows workflow for Gremlin Javascript will fail. There is a recurring failure from the scenario 'g_V_connectedComponent_hasXcomponentX' on the 'When iterated to list' step in 'ConnectedComponent.feature'. This can be observed in this Workflow Run: Link. When 'g_V_connectedComponent_hasXcomponentX' fails, sometimes other scenarios like 'g_V_dedup_connectedComponent_hasXcomponentX' can also fail.
On adding some server logs, on the failed tests we can observe that on the server side, the request is still processed but takes longer than the Cucumber threshold (Link ). We can also see that the slow down is not limited to just the specific Scenario (Link). For reference, these are the usual runtimes for the same Steps respectively, but on a different workflow run ('connectedComponent()' and 'dedup()').
This ticket is to track the investigation of the slowdown on Gremlin Server on Windows in GitHub Actions.