Build: https://ci-builds.apache.org/job/Solr/job/Solr-NightlyTests-main/1650/

1 tests failed.
FAILED:  org.apache.solr.handler.component.DistributedSuggestComponentTest.test

Error Message:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=101071, name=StressRunner, state=RUNNABLE, 
group=TGRP-DistributedSuggestComponentTest]

Stack Trace:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=101071, name=StressRunner, state=RUNNABLE, 
group=TGRP-DistributedSuggestComponentTest]
Caused by: org.apache.solr.client.solrj.SolrClient$RemoteSolrException: Error 
from server at https://127.0.0.1:46301/solr: 
org.apache.solr.client.solrj.SolrServerException: Connection refused
        at __randomizedtesting.SeedInfo.seed([9B8CBF8BD25B0181]:0)
        at 
app//org.apache.solr.client.solrj.apache.HttpSolrClient.executeMethod(HttpSolrClient.java:716)
        at 
app//org.apache.solr.client.solrj.apache.HttpSolrClient.request(HttpSolrClient.java:257)
        at 
app//org.apache.solr.client.solrj.apache.HttpSolrClient.request(HttpSolrClient.java:236)
        at 
app//org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:283)
        at 
app//org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:926)
        at 
app//org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:939)
        at 
app//org.apache.solr.BaseDistributedSearchTestCase.lambda$query$4(BaseDistributedSearchTestCase.java:657)
        at [email protected]/java.lang.Thread.run(Thread.java:1583)




Build Log:
[...truncated 5851 lines...]
ERROR: The following test(s) have failed:
  - org.apache.solr.handler.component.DistributedSuggestComponentTest.test 
(:solr:core)
    Test history: 
https://develocity.apache.org/scans/tests?search.rootProjectNames=solr-root&tests.container=org.apache.solr.handler.component.DistributedSuggestComponentTest&tests.test=test
 
http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.handler.component.DistributedSuggestComponentTest.test
    Test output: 
/home/jenkins/jenkins-agent/workspace/Solr/Solr-NightlyTests-main/solr/core/build/test-results/test/outputs/OUTPUT-org.apache.solr.handler.component.DistributedSuggestComponentTest.txt
    Reproduce with: ./gradlew :solr:core:test --tests 
"org.apache.solr.handler.component.DistributedSuggestComponentTest.test" 
-Ptests.haltonfailure=false "-Ptests.jvmargs=-XX:TieredStopAtLevel=1 
-XX:+UseParallelGC -XX:ActiveProcessorCount=1 -XX:ReservedCodeCacheSize=120m" 
-Ptests.seed=9B8CBF8BD25B0181 -Ptests.multiplier=2 
-Ptests.useSecurityManager=true -Ptests.nightly=true -Ptests.badapples=false 
-Ptests.file.encoding=UTF-8 
-Ptests.linedocsfile=/home/jenkins/jenkins-agent/workspace/Solr/Solr-NightlyTests-main/test-data/enwiki.random.lines.txt


Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.

For more on this, please refer to 
https://docs.gradle.org/8.10/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.

BUILD SUCCESSFUL in 1h 22m 7s
146 actionable tasks: 146 executed

Publishing build scan...
https://develocity.apache.org/s/jf6pnaxar6krk

Build step 'Invoke Gradle script' changed build result to SUCCESS
Archiving artifacts
‘**/*.events’ doesn’t match anything: ‘**’ exists but not ‘**/*.events’
No artifacts found that match the file pattern 
"**/*.events,heapdumps/**,**/hs_err_pid*". Configuration error?
Recording test results
[Checks API] No suitable checks publisher found.
Build step 'Publish JUnit test result report' changed build result to UNSTABLE
Email was triggered for: Unstable (Test Failures)
Sending email for trigger: Unstable (Test Failures)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to