[
https://issues.apache.org/jira/browse/SOLR-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739706#comment-17739706
]
Alex Deparvu edited comment on SOLR-15819 at 7/3/23 6:05 PM:
-------------------------------------------------------------
[~hossman] I took a look at this failing test and I agree with this analysis. I
went a step further and send a message to the dev list to propose removing the
test, as I don't see the usefulness in its current form.
https://lists.apache.org/thread/xhsrr6ksc5y11t29zz60oglw8ymkrwtf
We could consider adding a benchmark comparing CB with non-CB setup to compare
perf numbers, if this was in fact the intention behind the test.
was (Author: alex.parvulescu):
[~hossman] I took a look at this failing test and I agree with this analysis. I
went a step further and send a message to the dev list to propose removing the
test, as. I don't see the usefulness in its current form.
https://lists.apache.org/thread/xhsrr6ksc5y11t29zz60oglw8ymkrwtf
> spurious failures from TestCircuitBreaker.testResponseWithCBTiming
> ------------------------------------------------------------------
>
> Key: SOLR-15819
> URL: https://issues.apache.org/jira/browse/SOLR-15819
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
>
> As seen in both jenkins runs and locally on my machine,
> {{TestCircuitBreaker.testResponseWithCBTiming}} can fail in non-reproducible
> ways due to "Circuit Breakers tripped Memory Circuit Breaker triggered as JVM
> heap usage values are greater than allocated threshold.Seen JVM heap memory
> usage 424442256 and allocated threshold 402653184"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
