You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@solr.apache.org by Kevin Risden <kr...@apache.org> on 2022/03/03 17:36:47 UTC
Re: [JENKINS] Solr » Solr-Check-9.x - Build # 395 - Failure!
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>.
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
>
>