[
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. 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:
There exists a floating error that comes from the scenario
`g_V_connectedComponent_hasXcomponentX`. The Scenario times out at the
`iterated to list` step with a message:
```
Error: function timed out, ensure the promise resolves within 5000 milliseconds
```
This occurs 4/40 Runs on GitHub Actions.
> 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. 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)
