I pushed the fix a minute ago; at about the time you sent your email. No need to post a 9x backport PR in general for little issues like this. If a backport is more complicated then a PR for it is a good idea.
On Sat, May 24, 2025 at 12:15 PM Matthew Biscocho (BLOOMBERG/ 919 3RD A) < [email protected]> wrote: > Sorry about that. I got caught on the backport doing a bad cast not > possible with Java 11. Will make sure to run precommit and tests before > backporting next time. Here is the corresponding PR to fix the 9x build > https://github.com/apache/solr/pull/3363 > > From: [email protected] At: 05/24/25 11:19:58 UTC-4:00To: Matthew > Biscocho (BLOOMBERG/ 919 3RD A ) , [email protected] > Cc: [email protected] > Subject: Re: [JENKINS] Solr » Solr-Test-9.x - Build # 7477 - Still Failing! > > > Matthew, you broke the 9x build; every CI email for 9x builds are failing > for 2 days now. Sadly we don't have a CI failure notification to notify > the author of the offending commits. > When committing / pushing, it's imperative that you run "./gradlew > precommit" at a minimum; ideally run tests as well. > On Sat, May 24, 2025 at 10:19 AM Apache Jenkins Server < > [email protected]> wrote: > > Build: https://ci-builds.apache.org/job/Solr/job/Solr-Test-9.x/7477/ > > No tests ran. > > Build Log: > [...truncated 179 lines...] > BUILD FAILED in 48s > 60 actionable tasks: 60 executed > > Publishing build scan... > https://develocity.apache.org/s/z73gcgk5y6kr6 > > 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] > > >
