[
https://issues.apache.org/jira/browse/TINKERPOP-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rithin Kumar R S updated TINKERPOP-2779:
----------------------------------------
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
```
was:
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. 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
```
> Floating ConnectedComponent Feature Failures for GitHub Actions on windows
> --------------------------------------------------------------------------
>
> Key: TINKERPOP-2779
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2779
> Project: TinkerPop
> Issue Type: Improvement
> Components: javascript
> Environment: GitHub Actions - Windows
> Reporter: Rithin Kumar R S
> Priority: Minor
>
> 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
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
