[
https://issues.apache.org/jira/browse/SOLR-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355324#comment-17355324
]
Dawid Weiss commented on SOLR-15447:
------------------------------------
This is a synthetic name for anything that is class-level - static
initializers, before-class hooks, etc. You can't filter on this but it's still
informative to know where the problem happened. The stack trace contains the
details. I don't think this can be improved (the reproduce line could omit
.classMethod to allow rerunning the entire suite).
> Reproduce with line inaccurate for class methods
> ------------------------------------------------
>
> Key: SOLR-15447
> URL: https://issues.apache.org/jira/browse/SOLR-15447
> Project: Solr
> Issue Type: Test
> Components: Tests
> Reporter: Mike Drob
> Priority: Major
>
> I had this failure running tests recently:
> {noformat}
> - org.apache.solr.cloud.api.collections.ShardSplitTest.classMethod
> (:solr:core)
> Test output:
> /Users/mdrob/code/solr/solr/core/build/test-results/test/outputs/OUTPUT-org.apache.solr.cloud.api.collections.ShardSplitTest.txt
> Reproduce with: gradlew :solr:core:test --tests
> "org.apache.solr.cloud.api.collections.ShardSplitTest.classMethod"
> -Ptests.jvms=16 -Ptests.jvmargs=-XX:TieredStopAtLevel=1
> -Ptests.seed=40D22CF6F9086FB4 -Ptests.file.encoding=UTF-8 {noformat}
> There is no "classMethod" method, so the given command line fails to
> reproduce the failure. Unfortunately, I do not have the logs anymore, but I
> strongly expect this was a failure either in the test setup, teardown, or
> possibly something like the thread leak detector.
>
> We should figure out how we can provide a better reproduce with line for this
> type of failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
