-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flaky server test: ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated #3849
Labels
Comments
This was referenced Jun 22, 2023
FlorianHockmann
changed the title
Test failing on master: ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated
Flaky test: ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated
Jun 22, 2023
FlorianHockmann
changed the title
Flaky test: ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated
Flaky server test: ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated
Jun 22, 2023
FlorianHockmann
added a commit
to GDATASoftwareAG/janusgraph
that referenced
this issue
Jun 28, 2023
The test has been failing quite often lately, probably simply because it didn't wait long enough for the new graph to be created, at least for slow hardware like we have with GH Actions. Fixes JanusGraph#3849 Signed-off-by: Florian Hockmann <[email protected]>
9 tasks
FlorianHockmann
added a commit
that referenced
this issue
Jun 30, 2023
The test has been failing quite often lately, probably simply because it didn't wait long enough for the new graph to be created, at least for slow hardware like we have with GH Actions. Fixes #3849 Signed-off-by: Florian Hockmann <[email protected]>
janusgraph-automations
pushed a commit
that referenced
this issue
Jun 30, 2023
The test has been failing quite often lately, probably simply because it didn't wait long enough for the new graph to be created, at least for slow hardware like we have with GH Actions. Fixes #3849 Signed-off-by: Florian Hockmann <[email protected]> (cherry picked from commit 1ac6ed1)
FlorianHockmann
added a commit
that referenced
this issue
Jun 30, 2023
The test has been failing quite often lately, probably simply because it didn't wait long enough for the new graph to be created, at least for slow hardware like we have with GH Actions. Fixes #3849 Signed-off-by: Florian Hockmann <[email protected]> (cherry picked from commit 1ac6ed1)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Flaky Test
org.janusgraph.graphdb.tinkerpop.ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated
ConfigurationManagementGraphServerTest.bindingShouldExistAfterGraphIsCreated:79 » Execution org.apache.tinkerpop.gremlin.driver.exception.ResponseException: No such property: newGraph for class: Script7
master
master
with unrelated changes. It is failing for Java 8 and 11.It's part of these jobs:
tests (server, 8)
tests (server, -Pjava-11, 11)
Stack Trace
The text was updated successfully, but these errors were encountered: