GROOVY-7785: Stack overflow when using too many chained method calls (guard test to pin current behavior: indy only not classic)

Author: paulk-asert

src/test/groovy/bugs/Groovy7785.groovy

@@ -20,13 +20,22 @@ package bugs
 
 import org.junit.jupiter.api.Disabled
 import org.junit.jupiter.api.Test
+import org.junit.jupiter.api.condition.DisabledIfSystemProperty
 
 import static groovy.test.GroovyAssert.assertScript
 
 /**
  * Tests for GROOVY-7785: StackOverflowError with deeply nested chained method calls.
  * Each test uses chained method calls to verify the fix handles deep chains.
+ * <p>
+ * The fix (iterative chain flattening) is implemented in the invokedynamic
+ * writer only; classic bytecode generation still overflows the stack on very
+ * deep call chains. Classic is being phased out, so this is a documented
+ * limitation rather than a bug to fix — hence the tests are skipped when
+ * compiling with {@code groovy.target.indy=false}.
  */
+@DisabledIfSystemProperty(named = 'groovy.target.indy', matches = '(?i)false',
+    disabledReason = 'GROOVY-7785 deep-chain flattening is indy-only; classic codegen overflows on very deep chains')
 final class Groovy7785 {
 
     @Test