[
https://issues.apache.org/jira/browse/GROOVY-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083049#comment-18083049
]
ASF GitHub Bot commented on GROOVY-12023:
-----------------------------------------
testlens-app[bot] commented on PR #2549:
URL: https://github.com/apache/groovy/pull/2549#issuecomment-4524967259
## 🚨 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,
ubuntu-latest\)](https://github.com/apache/groovy/actions/runs/26329246400/job/77512319442?pr=2549)
| :groovy-groovysh:test | HelpCommandTest > helpListsKnownCommands\(\) | ❌ |
🏷️ Commit: 164311f6c7bfb5ac27d4f4da1ec93b29baf3924a
▶️ Tests: 36159 executed
🟡 Checks: 8/56 completed
### Test Failures
<details>
<summary><strong>HelpCommandTest > helpListsKnownCommands()</strong>
(:groovy-groovysh:test in <a
href="https://github.com/apache/groovy/actions/runs/26329246400/job/77512319442?pr=2549";>Build
and test / lts (17, ubuntu-latest)</a>)</summary>
```
Assertion failed:
assert !out.empty
|| |
|'' true
false
at
org.codehaus.groovy.runtime.InvokerHelper.createAssertError(InvokerHelper.java:400)
at
org.apache.groovy.groovysh.commands.HelpCommandTest.helpListsKnownCommands(HelpCommandTest.groovy:39)
```
</details>
### Muted Tests
> [!NOTE]
> Checks are currently running using the configuration below.
Select tests to mute in this pull request:
🔲 HelpCommandTest > helpListsKnownCommands\(\) <!
> create a PIC for indy
> ---------------------
>
> Key: GROOVY-12023
> URL: https://issues.apache.org/jira/browse/GROOVY-12023
> Project: Groovy
> Issue Type: Bug
> Reporter: Jochen Theodorou
> Assignee: Jochen Theodorou
> Priority: Major
>
> What we currently have is essentially a two layer system in which we have the
> target handle and cache for everything else. This can be seen as a PIC of
> size 1 with a fallback cache for megamorphic cases. Here I propose to
> implement a PIC of at least size 3 consisting of method handles where the
> guard will use the next PIC element as fallback instead of going to the
> cache. The goal is to reach a more stable configuration on the callsite for
> JIT to optimize.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
