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 <[email protected]> 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 <[email protected]>
> 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 <[email protected]>:
>> >
>> >
>> > 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 <
>> [email protected]> 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: [email protected]
>> >> For additional commands, e-mail: [email protected]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

Reply via email to