[TINKERPOP-2779] Floating ConnectedComponent Feature Failures for GitHub Actions on windows

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.5.4
• Fix Version/s: 3.7.0, 3.6.2, 3.5.5
• Component/s: javascript
• Environment: GitHub Actions - Windows

Language

javascript

• Assignee: Stephen Mallette
• Reporter: Rithin Kumar R S
• Created: 02/Aug/22 21:00
• Updated: 18/Aug/22 12:54
• Resolved: 18/Aug/22 12:54

Description

The GitHub Actions workflow for Gremlin Javascript produces Floating Cucumber JS Timeout Failures. The probability of occurrence is ~2%.

This error happens when a Scenario has a step that takes longer than 5s to resolve. This slowdown occurs in the Gremlin Server that is spun up to run integration tests. For the Failing cases, the server does process the request, but since it took longer than 5s to process, it ends up not having anywhere to return the results to as Cucumber severs the connection to the server after 5s.

A few tests are impacted by this problem mostly related to `ConnectedComponent.feature`. This issue has been observed in the Dotnet Driver as well so it seems to not be a client issue.

 

The failing Scenario times out at the `iterated to list` step with a message:
```
Error: function timed out, ensure the promise resolves within 5000 milliseconds
```