[
https://issues.apache.org/jira/browse/TINKERPOP-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579860#comment-17579860
]
ASF GitHub Bot commented on TINKERPOP-2779:
-------------------------------------------
L0Lmaker opened a new pull request, #1782:
URL: https://github.com/apache/tinkerpop/pull/1782
Temporary fix for the
[TINKERPOP-2779](https://issues.apache.org/jira/browse/TINKERPOP-2779).
Slowdown appears to be coming from the Gremlin Server that is spun up to run
the Cucumber tests. On logging some information from the server, I was able to
verify that the server receives and processes the Connected Component Traversal
([Link to log
line](https://github.com/L0Lmaker/tinkerpop/runs/7755756716?check_suite_focus=true#step:4:11942)).
Breakdown of what happens in the order it happens:
1. Client sends traversal to the server from Cucumber Step (Note: Cucumber
Steps currently have a default timeout of 5s).
2. Server receives the request and starts processing the traversal.
3. Slowdown on the Server causes traversal to be processed much longer than
usual.
4. 5s threshold on Cucumber Step is passed and Cucumber fails the scenario
with a timeout error.
5. Gremlin-JS on Windows Fails on GitHub Actions.
As of now, without any server changes, the only way to mitigate the
occasional GitHub Actions failure for Gremlin-JS Windows would be to increase
the Cucumber timeout to 10s. If there is anyone that has encountered similar
issues and could add some information that would be helpful.
[TINKERPOP-2779](https://issues.apache.org/jira/browse/TINKERPOP-2779) was
created specifically with `gremlin-javascript` in mind. Since then,
ConnectedComponent's occasional timeout failures have been observed in the
`Gremlin Dotnet` Driver as well. I have created a new ticket
([TINKERPOP-2784](https://issues.apache.org/jira/browse/TINKERPOP-2784))
documenting specifics of the `Gremlin Server` issue to keep track of it.
> 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)
