You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@solr.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2022/03/03 11:19:25 UTC
[JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/
No tests ran.
Build Log:
[...truncated 71 lines...]
BUILD FAILED in 10s
2 actionable tasks: 2 executed
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Posted by Kevin Risden <kr...@apache.org>.
Removing the gradle cache on lucene-solr-1 worked and the jobs that
were failing are now running correctly as far as I can tell.
For reference I created this temp job to remove the gradle cache:
https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup/
Kevin Risden
On Thu, Mar 3, 2022 at 6:08 PM Jan Høydahl <ja...@cominvent.com> wrote:
>
> I have seen similar things with the SmokeTester job, there was an error message about corrupted gradle cache in /home/jenkins/.gradle or something (the job log is not available anymore). So perhaps nuking the gradle cache is something to try
>
> Jan
>
> 3. mar. 2022 kl. 22:38 skrev Kevin Risden <kr...@apache.org>:
>
> Cleaning the workspace on lucene-solr-1 didn't seem to work.
>
> This job is also failing with a similar error:
>
> https://ci-builds.apache.org/job/Solr/job/Solr-Artifacts-9x/55/
>
> Is it possible the cache is messed up? Is there a gradle daemon stuck on the node?
>
> What is a good way to debug this?
>
> Kevin Risden
>
>
> On Thu, Mar 3, 2022 at 12:36 PM Kevin Risden <kr...@apache.org> wrote:
>>
>> So I've been trying to figure out these failures. It looks like it only happens on "lucene-solr-1" since it passes on "lucene-solr-2"
>>
>> Failed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ - lucene-solr-1
>> Passed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/ - lucene-solr-2
>>
>> The last few jobs I've checked that have failed with "No tests ran." have been on "lucene-solr-1"
>>
>> Is it possible the workspace is corrupted somehow? Can the workspace be cleaned out to check?
>>
>> Kevin Risden
>>
>>
>> On Thu, Mar 3, 2022 at 6:19 AM Apache Jenkins Server <je...@builds.apache.org> wrote:
>>>
>>> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/
>>>
>>> No tests ran.
>>>
>>> Build Log:
>>> [...truncated 71 lines...]
>>> BUILD FAILED in 10s
>>> 2 actionable tasks: 2 executed
>>> Build step 'Invoke Gradle script' changed build result to FAILURE
>>> Build step 'Invoke Gradle script' marked build as failure
>>> Archiving artifacts
>>> Recording test results
>>> ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
>>> Email was triggered for: Failure - Any
>>> Sending email for trigger: Failure - Any
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org
>>> For additional commands, e-mail: builds-help@solr.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
For additional commands, e-mail: dev-help@solr.apache.org
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Posted by Jan Høydahl <ja...@cominvent.com>.
I have seen similar things with the SmokeTester job, there was an error message about corrupted gradle cache in /home/jenkins/.gradle or something (the job log is not available anymore). So perhaps nuking the gradle cache is something to try
Jan
> 3. mar. 2022 kl. 22:38 skrev Kevin Risden <kr...@apache.org>:
>
> Cleaning the workspace on lucene-solr-1 didn't seem to work.
>
> This job is also failing with a similar error:
>
> https://ci-builds.apache.org/job/Solr/job/Solr-Artifacts-9x/55/ <https://ci-builds.apache.org/job/Solr/job/Solr-Artifacts-9x/55/>
>
> Is it possible the cache is messed up? Is there a gradle daemon stuck on the node?
>
> What is a good way to debug this?
>
> Kevin Risden
>
>
> On Thu, Mar 3, 2022 at 12:36 PM Kevin Risden <krisden@apache.org <ma...@apache.org>> wrote:
> So I've been trying to figure out these failures. It looks like it only happens on "lucene-solr-1" since it passes on "lucene-solr-2"
>
> Failed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ <https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/> - lucene-solr-1
> Passed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/ <https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/> - lucene-solr-2
>
> The last few jobs I've checked that have failed with "No tests ran." have been on "lucene-solr-1"
>
> Is it possible the workspace is corrupted somehow? Can the workspace be cleaned out to check?
>
> Kevin Risden
>
>
> On Thu, Mar 3, 2022 at 6:19 AM Apache Jenkins Server <jenkins@builds.apache.org <ma...@builds.apache.org>> wrote:
> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ <https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/>
>
> No tests ran.
>
> Build Log:
> [...truncated 71 lines...]
> BUILD FAILED in 10s
> 2 actionable tasks: 2 executed
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org <ma...@solr.apache.org>
> For additional commands, e-mail: builds-help@solr.apache.org <ma...@solr.apache.org>
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Posted by Kevin Risden <kr...@apache.org>.
Cleaning the workspace on lucene-solr-1 didn't seem to work.
This job is also failing with a similar error:
https://ci-builds.apache.org/job/Solr/job/Solr-Artifacts-9x/55/
Is it possible the cache is messed up? Is there a gradle daemon stuck on
the node?
What is a good way to debug this?
Kevin Risden
On Thu, Mar 3, 2022 at 12:36 PM Kevin Risden <kr...@apache.org> wrote:
> So I've been trying to figure out these failures. It looks like it only
> happens on "lucene-solr-1" since it passes on "lucene-solr-2"
>
> Failed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ -
> lucene-solr-1
> Passed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/ -
> lucene-solr-2
>
> The last few jobs I've checked that have failed with "No tests ran." have
> been on "lucene-solr-1"
>
> Is it possible the workspace is corrupted somehow? Can the workspace be
> cleaned out to check?
>
> Kevin Risden
>
>
> On Thu, Mar 3, 2022 at 6:19 AM Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/
>>
>> No tests ran.
>>
>> Build Log:
>> [...truncated 71 lines...]
>> BUILD FAILED in 10s
>> 2 actionable tasks: 2 executed
>> Build step 'Invoke Gradle script' changed build result to FAILURE
>> Build step 'Invoke Gradle script' marked build as failure
>> Archiving artifacts
>> Recording test results
>> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
>> files were found. Configuration error?
>> Email was triggered for: Failure - Any
>> Sending email for trigger: Failure - Any
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org
>> For additional commands, e-mail: builds-help@solr.apache.org
>
>
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Posted by Kevin Risden <kr...@apache.org>.
Cleaning the workspace on lucene-solr-1 didn't seem to work.
This job is also failing with a similar error:
https://ci-builds.apache.org/job/Solr/job/Solr-Artifacts-9x/55/
Is it possible the cache is messed up? Is there a gradle daemon stuck on
the node?
What is a good way to debug this?
Kevin Risden
On Thu, Mar 3, 2022 at 12:36 PM Kevin Risden <kr...@apache.org> wrote:
> So I've been trying to figure out these failures. It looks like it only
> happens on "lucene-solr-1" since it passes on "lucene-solr-2"
>
> Failed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ -
> lucene-solr-1
> Passed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/ -
> lucene-solr-2
>
> The last few jobs I've checked that have failed with "No tests ran." have
> been on "lucene-solr-1"
>
> Is it possible the workspace is corrupted somehow? Can the workspace be
> cleaned out to check?
>
> Kevin Risden
>
>
> On Thu, Mar 3, 2022 at 6:19 AM Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/
>>
>> No tests ran.
>>
>> Build Log:
>> [...truncated 71 lines...]
>> BUILD FAILED in 10s
>> 2 actionable tasks: 2 executed
>> Build step 'Invoke Gradle script' changed build result to FAILURE
>> Build step 'Invoke Gradle script' marked build as failure
>> Archiving artifacts
>> Recording test results
>> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
>> files were found. Configuration error?
>> Email was triggered for: Failure - Any
>> Sending email for trigger: Failure - Any
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org
>> For additional commands, e-mail: builds-help@solr.apache.org
>
>
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Posted by Kevin Risden <kr...@apache.org>.
So I've been trying to figure out these failures. It looks like it only
happens on "lucene-solr-1" since it passes on "lucene-solr-2"
Failed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ -
lucene-solr-1
Passed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/ -
lucene-solr-2
The last few jobs I've checked that have failed with "No tests ran." have
been on "lucene-solr-1"
Is it possible the workspace is corrupted somehow? Can the workspace be
cleaned out to check?
Kevin Risden
On Thu, Mar 3, 2022 at 6:19 AM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/
>
> No tests ran.
>
> Build Log:
> [...truncated 71 lines...]
> BUILD FAILED in 10s
> 2 actionable tasks: 2 executed
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org
> For additional commands, e-mail: builds-help@solr.apache.org
[JENKINS] Solr » Solr-Check-9.x - Build # 399 - Still Failing!
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/399/
No tests ran.
Build Log:
[...truncated 71 lines...]
BUILD FAILED in 7s
2 actionable tasks: 2 executed
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[JENKINS] Solr » Solr-Check-9.x - Build # 398 - Still Failing!
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/398/
No tests ran.
Build Log:
[...truncated 70 lines...]
BUILD FAILED in 17s
2 actionable tasks: 2 executed
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[JENKINS] Solr » Solr-Check-9.x - Build # 397 - Failure!
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/397/
No tests ran.
Build Log:
[...truncated 74 lines...]
BUILD FAILED in 9s
2 actionable tasks: 2 executed
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[JENKINS] Solr » Solr-Check-9.x - Build # 396 - Unstable!
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/
1 tests failed.
FAILED: org.apache.solr.core.TestCoreDiscovery.testTooManyTransientCores
Error Message:
java.lang.AssertionError: There should only be 3 cores loaded, coreLOS and two coreT? cores expected:<3> but was:<4>
Stack Trace:
java.lang.AssertionError: There should only be 3 cores loaded, coreLOS and two coreT? cores expected:<3> but was:<4>
at __randomizedtesting.SeedInfo.seed([AB94F762D01553C6:8140B7C69D131BDA]:0)
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at org.apache.solr.core.TestCoreDiscovery.testTooManyTransientCores(TestCoreDiscovery.java:330)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1754)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:942)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:978)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:992)
at com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:44)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:370)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:819)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:470)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:951)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:836)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:887)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:898)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
at org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:370)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:826)
at java.base/java.lang.Thread.run(Thread.java:834)
Build Log:
[...truncated 1651 lines...]
ERROR: The following test(s) have failed:
- org.apache.solr.core.TestCoreDiscovery.testTooManyTransientCores (:solr:core)
Test output: /home/jenkins/jenkins-slave/workspace/Solr/Solr-Check-9.x/solr/core/build/test-results/test/outputs/OUTPUT-org.apache.solr.core.TestCoreDiscovery.txt
Reproduce with: gradlew :solr:core:test --tests "org.apache.solr.core.TestCoreDiscovery.testTooManyTransientCores" -Ptests.jvms=4 -Ptests.haltonfailure=false -Ptests.jvmargs=-XX:TieredStopAtLevel=1 -Ptests.seed=AB94F762D01553C6 -Ptests.multiplier=2 -Ptests.badapples=false -Ptests.file.encoding=UTF-8
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 53m 40s
532 actionable tasks: 532 executed
Build step 'Invoke Gradle script' changed build result to SUCCESS
Archiving artifacts
java.lang.InterruptedException: no matches found within 10000
at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3079)
at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2958)
at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2939)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3329)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to lucene-solr-2
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1797)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:1001)
at hudson.FilePath.act(FilePath.java:1165)
at hudson.FilePath.act(FilePath.java:1154)
at hudson.FilePath.validateAntFileMask(FilePath.java:2937)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:268)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:806)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:755)
at hudson.model.Build$BuildExecution.post2(Build.java:178)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:699)
at hudson.model.Run.execute(Run.java:1913)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:99)
at hudson.model.Executor.run(Executor.java:432)
Caused: hudson.FilePath$TunneledInterruptedException
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3331)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:376)
at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused: java.lang.InterruptedException: java.lang.InterruptedException: no matches found within 10000
at hudson.FilePath.act(FilePath.java:1167)
at hudson.FilePath.act(FilePath.java:1154)
at hudson.FilePath.validateAntFileMask(FilePath.java:2937)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:268)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:806)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:755)
at hudson.model.Build$BuildExecution.post2(Build.java:178)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:699)
at hudson.model.Run.execute(Run.java:1913)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:99)
at hudson.model.Executor.run(Executor.java:432)
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)
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
Posted by Kevin Risden <kr...@apache.org>.
So I've been trying to figure out these failures. It looks like it only
happens on "lucene-solr-1" since it passes on "lucene-solr-2"
Failed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/ -
lucene-solr-1
Passed: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/396/ -
lucene-solr-2
The last few jobs I've checked that have failed with "No tests ran." have
been on "lucene-solr-1"
Is it possible the workspace is corrupted somehow? Can the workspace be
cleaned out to check?
Kevin Risden
On Thu, Mar 3, 2022 at 6:19 AM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/395/
>
> No tests ran.
>
> Build Log:
> [...truncated 71 lines...]
> BUILD FAILED in 10s
> 2 actionable tasks: 2 executed
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org
> For additional commands, e-mail: builds-help@solr.apache.org