akib6075

Flaky test evidence using the NonDex tool: https://github.com/akib6075/hippo4j/actions/runs/5135847635 After fixing: https://github.com/akib6075/hippo4j/actions/runs/5190631210 @magestacks

@magestacks In your test for assertGetPoolContent() fails to pass this line for some case which means your current code sometime pass "Assert.isTrue(testText.equals(ContentUtil.getPoolContent(threadPoolParameterInfo)));" line some cases or won't pass some cases....

@magestacks there is a loophole in the assertGetPoolContent() which is the testText is a collection of threadpoolparameter info which has a specific order of the keys. But the ContentUtil.getPoolContent() returns...

Actually I changed these two files to resolve the flaky issue. So what else I can do to resolve this? Can you give me any clue? TIA.

Thank you for your email On Thu, 25 May, 2023 at 11:43 AM, weihubeats ***@***.***> wrote: > You can resolve conflicts by pulling the latest code from the remote >...

After doing so it's saying "Already up to date." No conflicts in my local after pulling remote develop branch.

@weihubeats there is a loophole in the assertGetPoolContent() which is the testText is a collection of threadpoolparameter info which has a specific order of the keys. But the ContentUtil.getPoolContent() returns...

@weihubeats Thank you for your feedback. I understand your concern about the large number of file changes. I've reviewed the commits and believe they are necessary to address the flaky...