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