[ 
https://issues.apache.org/jira/browse/GROOVY-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089391#comment-18089391
 ] 

ASF GitHub Bot commented on GROOVY-12092:
-----------------------------------------

testlens-app[bot] commented on PR #2614:
URL: https://github.com/apache/groovy/pull/2614#issuecomment-4719475449

   ## 🚨 TestLens detected 1 failed test 🚨
   
   Here is what you can do:
   
   1) Inspect the test failures carefully.
   2) If you are convinced that some of the tests are flaky, you can mute them 
below.
   3) Finally, trigger a rerun by checking the rerun checkbox.
   
   ### Test Summary
   
   | Check | Project/Task | Test | Runs |
   |---|---|---|---|
   | [Build and test / lts \(17, windows-latest, 
1\)](https://github.com/apache/groovy/actions/runs/27620551251/job/81667942698?pr=2614)
 | :test | GenericsSTCTest > testReturnTypeInferenceWithMethodGenerics18\(\) | 
❌ |
   
   🏷️ Commit: 4e71956438a9b68869639108afd6ec996b907f8b
   ▶️ Tests:  90695 executed
   🟡 Checks: 20/28 completed
   
   ### Test Failures
   
   <details>
   
   <summary><strong>GenericsSTCTest > 
testReturnTypeInferenceWithMethodGenerics18()</strong> (:test in <a 
href="https://github.com/apache/groovy/actions/runs/27620551251/job/81667942698?pr=2614";>Build
 and test / lts (17, windows-latest, 1)</a>)</summary>
   
   ```
   org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
failed:
   TestScriptddcc4eda9cf9472e95a2ddce5f1b7cd2.groovy: 5: unable to resolve 
class ListMultimap<java.lang.String, java.lang.Integer>
    @ line 5, column 43.
                  ListMultimap<String, Integer> mmap = 
ArrayListMultimap.create()
                                                ^
   
   1 error
   
        at 
org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:333)
        at 
org.codehaus.groovy.control.CompilationUnit$ISourceUnitOperation.doPhaseOperation(CompilationUnit.java:989)
        at 
org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:749)
        at 
org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:723)
        at 
groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:423)
        at 
groovy.lang.GroovyClassLoader.lambda$parseClass$3(GroovyClassLoader.java:364)
        at 
org.codehaus.groovy.runtime.memoize.ConcurrentCommonCache.getAndPut(ConcurrentCommonCache.java:143)
        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:364)
        at groovy.lang.GroovyShell.parseClass(GroovyShell.java:665)
        at groovy.lang.GroovyShell.parse(GroovyShell.java:678)
        at groovy.lang.GroovyShell.parse(GroovyShell.java:690)
        at groovy.lang.GroovyShell.evaluate(GroovyShell.java:552)
        at groovy.lang.GroovyShell.evaluate(GroovyShell.java:588)
        at groovy.lang.GroovyShell.evaluate(GroovyShell.java:572)
        at 
groovy.transform.stc.StaticTypeCheckingTestCase.assertScript(StaticTypeCheckingTestCase.groovy:78)
        at 
groovy.transform.stc.GenericsSTCTest.testReturnTypeInferenceWithMethodGenerics18(GenericsSTCTest.groovy:701)
   ```
   
   </details>
   
   ### Muted Tests
   > [!NOTE]
   > Checks are currently running using the configuration below.
   
   Select tests to mute in this pull request:
   
   🔲 GenericsSTCTest > testReturnTypeInferenceWithMethodGenerics18\(\) <!

> Allow a "groovy.indy.callsite.cache.cleaner.thread" flag to turn off the 
> PIC-Cleaner thread
> -------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-12092
>                 URL: https://issues.apache.org/jira/browse/GROOVY-12092
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Paul King
>            Assignee: Paul King
>            Priority: Major
>
> The default would be true, same as current behavior.
> If using a deadlock detection library, e.g. during testing, you could switch 
> it off and the PIC-Cleaner thread won't be detected as a false positive 
> deadlocked thread.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to