(tinkerpop) branch master updated: Skip 1+1 init probe for grammar-based groovy-test engine CTR

[kenhuuu]

This is an automated email from the ASF dual-hosted git repository.

kenhuuu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git


The following commit(s) were added to refs/heads/master by this push:
     new 98f06de01b Skip 1+1 init probe for grammar-based groovy-test engine CTR
98f06de01b is described below

commit 98f06de01bbb818aa6ff3f9ad238ec5cd562a176
Author: Ken Hu <106191785+kenh...@users.noreply.github.com>
AuthorDate: Wed Jun 17 11:38:28 2026 -0700

    Skip 1+1 init probe for grammar-based groovy-test engine CTR
    
    This was causing lots of bloat to the test logs as each test that
    started the server would add a large stack trace to the logs.
---
 .../apache/tinkerpop/gremlin/server/util/ServerGremlinExecutor.java  | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git 
a/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/util/ServerGremlinExecutor.java
 
b/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/util/ServerGremlinExecutor.java
index 570cf8d7da..3995337566 100644
--- 
a/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/util/ServerGremlinExecutor.java
+++ 
b/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/util/ServerGremlinExecutor.java
@@ -173,7 +173,10 @@ public class ServerGremlinExecutor {
             try {
                 // gremlin-lang does not need to be initialized. not so nice, 
but gremlin-lang is the only exception
                 // and ultimately, gremlin-lang will likely end up the only 
choice in gremlin-server.
-                if (!engineName.equals("gremlin-lang")) {
+                // groovy-test (used for testing purposes only) also 
interprets input via the Gremlin grammar, so it
+                // cannot evaluate the "1+1" init probe and likewise does not 
need init-script priming (its engine
+                // setup happens at construction, which is triggered by 
registerMetrics below).
+                if (!engineName.equals("gremlin-lang") && 
!engineName.equals("groovy-test")) {
                     // use no timeout on the engine initialization - perhaps 
this can be a configuration later
                     final GremlinExecutor.LifeCycle lifeCycle = 
GremlinExecutor.LifeCycle.build().
                             evaluationTimeoutOverride(0L).create();