You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by "zrlw (via GitHub)" <gi...@apache.org> on 2025/03/04 15:23:13 UTC
[I] [Bug] the waiting time of EagerThreadPoolExecutorTest#testEagerThreadPoolFast is insufficient [dubbo]
zrlw opened a new issue, #15204:
URL: https://github.com/apache/dubbo/issues/15204
### Pre-check
- [x] I am sure that all the content I provide is in English.
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues.
### Apache Dubbo Component
Java SDK (apache/dubbo)
### Dubbo Version
dubbo 3.3
### Steps to reproduce this issue
EagerThreadPoolExecutorTest.testEagerThreadPoolFast occasionally failed because of waiting timeout, see https://github.com/apache/dubbo/actions/runs/13647339272/job/38148937437
```
Error: org.apache.dubbo.common.threadpool.support.eager.EagerThreadPoolExecutorTest.testEagerThreadPoolFast -- Time elapsed: 10.07 s <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in org.apache.dubbo.common.threadpool.support.eager.EagerThreadPoolExecutorTest was not fulfilled within 10 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
at org.apache.dubbo.common.threadpool.support.eager.EagerThreadPoolExecutorTest.testEagerThreadPoolFast(EagerThreadPoolExecutorTest.java:139)
```
the result of LoadStatusCheckerTest shows that current host(172.27.192.1) has 4 cores (cpu:4),
```
[INFO] Running org.apache.dubbo.common.status.support.LoadStatusCheckerTest
... ...
INFO: [DUBBO] load status message: load:0.0,cpu:4, dubbo version: 3.3.4-SNAPSHOT, current host: 172.27.192.1
```
i tested EagerThreadPoolExecutorTest.testEagerThreadPoolFast on my own windows which has 4 cores, the elapsed time of new 10 threads rang from 4 seconds to 14 seconds.
### What you expected to happen
decrease maximum pool size of EagerThreadPoolExecutorTest or increase waiting time.
### Anything else
_No response_
### Are you willing to submit a pull request to fix on your own?
- [x] Yes I am willing to submit a pull request on my own!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org
Re: [I] [Bug] the waiting time of EagerThreadPoolExecutorTest#testEagerThreadPoolFast is insufficient [dubbo]
Posted by "AlbumenJ (via GitHub)" <gi...@apache.org>.
AlbumenJ closed issue #15204: [Bug] the waiting time of EagerThreadPoolExecutorTest#testEagerThreadPoolFast is insufficient
URL: https://github.com/apache/dubbo/issues/15204
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org