Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/6242/

1 tests failed.
FAILED:  
org.apache.solr.cloud.SplitShardWithNodeRoleTest.testSolrClusterWithNodeRoleWithPull

Error Message:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=10359, name=fsyncService-6557-thread-1, 
state=RUNNABLE, group=TGRP-SplitShardWithNodeRoleTest]

Stack Trace:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=10359, name=fsyncService-6557-thread-1, 
state=RUNNABLE, group=TGRP-SplitShardWithNodeRoleTest]
        at 
__randomizedtesting.SeedInfo.seed([358678FA01CC17D1:EF20EADEA5025AAC]:0)
Caused by: org.apache.lucene.store.AlreadyClosedException: this Directory is 
closed
        at __randomizedtesting.SeedInfo.seed([358678FA01CC17D1]:0)
        at 
app//org.apache.lucene.store.BaseDirectory.ensureOpen(BaseDirectory.java:50)
        at 
app//org.apache.lucene.store.ByteBuffersDirectory.sync(ByteBuffersDirectory.java:237)
        at 
app//org.apache.lucene.tests.store.MockDirectoryWrapper.sync(MockDirectoryWrapper.java:214)
        at 
app//org.apache.solr.handler.IndexFetcher$DirectoryFile.sync(IndexFetcher.java:2034)
        at 
app//org.apache.solr.handler.IndexFetcher$FileFetcher.lambda$fetch$0(IndexFetcher.java:1803)
        at 
app//org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:380)
        at 
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at [email protected]/java.lang.Thread.run(Thread.java:829)




Build Log:
[...truncated 5725 lines...]
ERROR: The following test(s) have failed:
  - 
org.apache.solr.cloud.SplitShardWithNodeRoleTest.testSolrClusterWithNodeRoleWithPull
 (:solr:core)
    Test history: 
https://ge.apache.org/scans/tests?search.rootProjectNames=solr-root&tests.container=org.apache.solr.cloud.SplitShardWithNodeRoleTest&tests.test=testSolrClusterWithNodeRoleWithPull
 
http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.cloud.SplitShardWithNodeRoleTest.testSolrClusterWithNodeRoleWithPull
    Test output: 
/home/jenkins/jenkins-slave/workspace/Solr/Solr-Check-9.x/solr/core/build/test-results/test/outputs/OUTPUT-org.apache.solr.cloud.SplitShardWithNodeRoleTest.txt
    Reproduce with: ./gradlew :solr:core:test --tests 
"org.apache.solr.cloud.SplitShardWithNodeRoleTest.testSolrClusterWithNodeRoleWithPull"
 -Ptests.jvms=4 -Ptests.haltonfailure=false 
"-Ptests.jvmargs=-XX:TieredStopAtLevel=1 -XX:+UseParallelGC 
-XX:ActiveProcessorCount=1 -XX:ReservedCodeCacheSize=120m" 
-Ptests.seed=358678FA01CC17D1 -Ptests.multiplier=2 -Ptests.badapples=false 
-Ptests.file.encoding=UTF-8


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.4/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.

BUILD SUCCESSFUL in 1h 14m 14s
742 actionable tasks: 742 executed

Publishing build scan...
https://ge.apache.org/s/arpdikgnaempm

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