shubhamvishu commented on issue #15661: URL: https://github.com/apache/lucene/issues/15661#issuecomment-3845158610
> Relax the clone-count threshold slightly in TestForTooMuchCloning for the 10.x branch to account for legitimate variability observed in CI runs, while still keeping the test effective at catching real regressions. @ML-dev-crypto It's important to identify what change is causing the increased clone calls rather than simply raising the test threshold. We need to understand the root cause(basically why this is not failing/reproducible on main) before we can justify increasing threshold. That's exactly why this test exists. Something like `git bisect` (https://git-scm.com/docs/git-bisect) could help in such case. > Improve diagnostics by logging additional context (e.g., seed, multiplier, and query parameters) when the assertion fails, making future debugging easier. This information is already present in the above issue description. See the "Gradle command to reproduce" section. Please feel free to share if you have any insights on why this test could be failing consistently on 10x branch or just open a PR if you have a fix. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
