[
https://issues.apache.org/jira/browse/SOLR-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870295#comment-17870295
]
Chris M. Hostetter commented on SOLR-17368:
-------------------------------------------
There is no way for typical users to force jenkins to run builds (particularly
against PR branches before committing) but if the problem is leaking metrics
between test classes that's easy enough for you to test locally – i mentioned
how to do it in the original jira...
https://issues.apache.org/jira/browse/SOLR-10654?focusedCommentId=17865236&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17865236
{quote}In the case of {{TestPrometheusResponseWriter}} – it's pretty easy to
reproduce the problem on _any_ JVM by running multiple "jetty" based test in
the same Test JVM ...
{quote}
On current main, this fails pretty consistently for me...
{noformat}
./gradlew -p solr/core test -Ptests.jvms=1 -Ptests.verbose=true --tests
TestPrometheusResponseWriter --tests \*Jetty\*{noformat}
> TestPrometheusResponseWriter redesign
> -------------------------------------
>
> Key: SOLR-17368
> URL: https://issues.apache.org/jira/browse/SOLR-17368
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Priority: Major
> Labels: pull-request-available
> Fix For: 9.7
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> TestPrometheusResponseWriter currently fails in 100% of all jenkins builds
> due to how it is designed, and depending on what other tests may run before
> it in the same JVM.
> This problem only affects the test, not the functionality of the underlying
> code.
> See SOLR-10654 for background discussions of the problems with this test, and
> options for improving it's design relative to it's purpose.
--
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
