Mailing List Archive

I was able to log in to the ASF Jenkins Console and created this job
that just deletes the whole gradle cache folder on nodes that are
labeled "lucene" (please see the job configuration).
https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/

I didn't set a schedule for the job and haven't executed it yet (it
may affect all running Lucene jobs) but I think I or anyone with an
ASF account can manually run it.

2022?6?6?(?) 15:18 Dawid Weiss <dawid.weiss@gmail.com>:
>
>
> This seems like a gradle cache problem somehow:
>
> Could not load compiled classes for script '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle' from cache.
>
>
> I'm not sure how to fix it on those agent machines - I see a jenkins job with this name:
>
>
> https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup
>
>
> But this is disabled... Has anybody experienced this before (whoever created that job)?
>
>
> Dawid
>
>
> On Mon, Jun 6, 2022 at 6:54 AM Apache Jenkins Server <jenkins@builds.apache.org> wrote:
>>
>> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/5746/
>>
>> No tests ran.
>>
>> Build Log:
>> [...truncated 73 lines...]
>> BUILD FAILED in 12s
>> 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@lucene.apache.org
>> For additional commands, e-mail: builds-help@lucene.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

I created the
https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup
job
since a similar error was seen a few months ago:

https://lists.apache.org/thread/jor6ct8l2vpq7x98hxdfn8xnp0ln6xqj

It did fix the problem, but was never able to identify the root cause.

Kevin Risden


On Mon, Jun 6, 2022 at 9:56 AM Tomoko Uchida <tomoko.uchida.1111@gmail.com>
wrote:

> I was able to log in to the ASF Jenkins Console and created this job
> that just deletes the whole gradle cache folder on nodes that are
> labeled "lucene" (please see the job configuration).
> https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/
>
> I didn't set a schedule for the job and haven't executed it yet (it
> may affect all running Lucene jobs) but I think I or anyone with an
> ASF account can manually run it.
>
> 2022?6?6?(?) 15:18 Dawid Weiss <dawid.weiss@gmail.com>:
> >
> >
> > This seems like a gradle cache problem somehow:
> >
> > Could not load compiled classes for script
> '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle'
> from cache.
> >
> >
> > I'm not sure how to fix it on those agent machines - I see a jenkins job
> with this name:
> >
> >
> >
> https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup
> >
> >
> > But this is disabled... Has anybody experienced this before (whoever
> created that job)?
> >
> >
> > Dawid
> >
> >
> > On Mon, Jun 6, 2022 at 6:54 AM Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
> >>
> >> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/5746/
> >>
> >> No tests ran.
> >>
> >> Build Log:
> >> [...truncated 73 lines...]
> >> BUILD FAILED in 12s
> >> 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@lucene.apache.org
> >> For additional commands, e-mail: builds-help@lucene.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

Thanks for clarifying (and fixing) - Tomoko, Kevin. I'm not sure what's
causing this either.

Dawid

On Mon, Jun 6, 2022 at 4:16 PM Kevin Risden <krisden@apache.org> wrote:

> I created the
> https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup job
> since a similar error was seen a few months ago:
>
> https://lists.apache.org/thread/jor6ct8l2vpq7x98hxdfn8xnp0ln6xqj
>
> It did fix the problem, but was never able to identify the root cause.
>
> Kevin Risden
>
>
> On Mon, Jun 6, 2022 at 9:56 AM Tomoko Uchida <tomoko.uchida.1111@gmail.com>
> wrote:
>
>> I was able to log in to the ASF Jenkins Console and created this job
>> that just deletes the whole gradle cache folder on nodes that are
>> labeled "lucene" (please see the job configuration).
>> https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/
>>
>> I didn't set a schedule for the job and haven't executed it yet (it
>> may affect all running Lucene jobs) but I think I or anyone with an
>> ASF account can manually run it.
>>
>> 2022?6?6?(?) 15:18 Dawid Weiss <dawid.weiss@gmail.com>:
>> >
>> >
>> > This seems like a gradle cache problem somehow:
>> >
>> > Could not load compiled classes for script
>> '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle'
>> from cache.
>> >
>> >
>> > I'm not sure how to fix it on those agent machines - I see a jenkins
>> job with this name:
>> >
>> >
>> >
>> https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup
>> >
>> >
>> > But this is disabled... Has anybody experienced this before (whoever
>> created that job)?
>> >
>> >
>> > Dawid
>> >
>> >
>> > On Mon, Jun 6, 2022 at 6:54 AM Apache Jenkins Server <
>> jenkins@builds.apache.org> wrote:
>> >>
>> >> Build:
>> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/5746/
>> >>
>> >> No tests ran.
>> >>
>> >> Build Log:
>> >> [...truncated 73 lines...]
>> >> BUILD FAILED in 12s
>> >> 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@lucene.apache.org
>> >> For additional commands, e-mail: builds-help@lucene.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>

I don't think anyone ran the job to clean up the gradle cache today,
and the job still fails with:

A problem occurred evaluating root project 'lucene-root'.
> Could not load compiled classes for script '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle' from cache.

As a trial, I will manually run this job and see the results.
https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/

Tomoko

2022?6?7?(?) 3:56 Dawid Weiss <dawid.weiss@gmail.com>:
>
>
> Thanks for clarifying (and fixing) - Tomoko, Kevin. I'm not sure what's causing this either.
>
> Dawid
>
> On Mon, Jun 6, 2022 at 4:16 PM Kevin Risden <krisden@apache.org> wrote:
>>
>> I created the https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup job since a similar error was seen a few months ago:
>>
>> https://lists.apache.org/thread/jor6ct8l2vpq7x98hxdfn8xnp0ln6xqj
>>
>> It did fix the problem, but was never able to identify the root cause.
>>
>> Kevin Risden
>>
>>
>> On Mon, Jun 6, 2022 at 9:56 AM Tomoko Uchida <tomoko.uchida.1111@gmail.com> wrote:
>>>
>>> I was able to log in to the ASF Jenkins Console and created this job
>>> that just deletes the whole gradle cache folder on nodes that are
>>> labeled "lucene" (please see the job configuration).
>>> https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/
>>>
>>> I didn't set a schedule for the job and haven't executed it yet (it
>>> may affect all running Lucene jobs) but I think I or anyone with an
>>> ASF account can manually run it.
>>>
>>> 2022?6?6?(?) 15:18 Dawid Weiss <dawid.weiss@gmail.com>:
>>> >
>>> >
>>> > This seems like a gradle cache problem somehow:
>>> >
>>> > Could not load compiled classes for script '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle' from cache.
>>> >
>>> >
>>> > I'm not sure how to fix it on those agent machines - I see a jenkins job with this name:
>>> >
>>> >
>>> > https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup
>>> >
>>> >
>>> > But this is disabled... Has anybody experienced this before (whoever created that job)?
>>> >
>>> >
>>> > Dawid
>>> >
>>> >
>>> > On Mon, Jun 6, 2022 at 6:54 AM Apache Jenkins Server <jenkins@builds.apache.org> wrote:
>>> >>
>>> >> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/5746/
>>> >>
>>> >> No tests ran.
>>> >>
>>> >> Build Log:
>>> >> [...truncated 73 lines...]
>>> >> BUILD FAILED in 12s
>>> >> 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@lucene.apache.org
>>> >> For additional commands, e-mail: builds-help@lucene.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

The gradle cache was cleaned up on the two Jenkins servers (nodes)
that run jobs of Lucene and Solr.
It looks like all jobs are getting back to normal after removing the
cache folder.
I'd schedule the cleaning up job to run periodically (once per week, maybe?).

Tomoko

2022?6?7?(?) 6:20 Tomoko Uchida <tomoko.uchida.1111@gmail.com>:
>
> I don't think anyone ran the job to clean up the gradle cache today,
> and the job still fails with:
>
> A problem occurred evaluating root project 'lucene-root'.
> > Could not load compiled classes for script '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle' from cache.
>
> As a trial, I will manually run this job and see the results.
> https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/
>
> Tomoko
>
> 2022?6?7?(?) 3:56 Dawid Weiss <dawid.weiss@gmail.com>:
> >
> >
> > Thanks for clarifying (and fixing) - Tomoko, Kevin. I'm not sure what's causing this either.
> >
> > Dawid
> >
> > On Mon, Jun 6, 2022 at 4:16 PM Kevin Risden <krisden@apache.org> wrote:
> >>
> >> I created the https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup job since a similar error was seen a few months ago:
> >>
> >> https://lists.apache.org/thread/jor6ct8l2vpq7x98hxdfn8xnp0ln6xqj
> >>
> >> It did fix the problem, but was never able to identify the root cause.
> >>
> >> Kevin Risden
> >>
> >>
> >> On Mon, Jun 6, 2022 at 9:56 AM Tomoko Uchida <tomoko.uchida.1111@gmail.com> wrote:
> >>>
> >>> I was able to log in to the ASF Jenkins Console and created this job
> >>> that just deletes the whole gradle cache folder on nodes that are
> >>> labeled "lucene" (please see the job configuration).
> >>> https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/
> >>>
> >>> I didn't set a schedule for the job and haven't executed it yet (it
> >>> may affect all running Lucene jobs) but I think I or anyone with an
> >>> ASF account can manually run it.
> >>>
> >>> 2022?6?6?(?) 15:18 Dawid Weiss <dawid.weiss@gmail.com>:
> >>> >
> >>> >
> >>> > This seems like a gradle cache problem somehow:
> >>> >
> >>> > Could not load compiled classes for script '/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Check-main/gradle/validation/validate-source-patterns.gradle' from cache.
> >>> >
> >>> >
> >>> > I'm not sure how to fix it on those agent machines - I see a jenkins job with this name:
> >>> >
> >>> >
> >>> > https://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup
> >>> >
> >>> >
> >>> > But this is disabled... Has anybody experienced this before (whoever created that job)?
> >>> >
> >>> >
> >>> > Dawid
> >>> >
> >>> >
> >>> > On Mon, Jun 6, 2022 at 6:54 AM Apache Jenkins Server <jenkins@builds.apache.org> wrote:
> >>> >>
> >>> >> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/5746/
> >>> >>
> >>> >> No tests ran.
> >>> >>
> >>> >> Build Log:
> >>> >> [...truncated 73 lines...]
> >>> >> BUILD FAILED in 12s
> >>> >> 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@lucene.apache.org
> >>> >> For additional commands, e-mail: builds-help@lucene.apache.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org