Thank you Nick for the report. I left comments on Jiras. In the future, when you create a Jira please fill in the “Affects Version(s)” field (and perhaps Component/s if applicable) so that it’s easier to track. Best if the Jira report “affects” the latest releases on major version(s) (e.g. 9.11 and 10.1), otherwise the reviewer will have to verify the report with the latest versions anyway.
Cheers, Andrzej > On 27 Oct 2026, at 08:54, Nick Boss <[email protected]> wrote: > > I ran the RC3 smoke tester on aarch64 Linux (JDK 21.0.12.1), with the > workspace on NFS. It failed all five runs on the release artifacts. I then > assembled a build from source with candidate fixes on top, instead of using > the tarball, to test them. The findings are written up in Jira: > > - Replica recovery fails on a filesystem that refuses hard links; > IndexFetcher has no copy fallback. SOLR-18586. A fix branch is linked on > the ticket. > - CoreAdmin unload after a failed reload can leave the previous core open. > SOLR-18587. The fix branch and a diff are linked on the ticket. > - The JS client build fails when NODE_ENV=production. SOLR-18593. A > one-line fix is prepared, on the same branch as the first item. > - A metrics-related failure appeared once in five runs here. It root-caused > to a shutdown leak, SOLR-18564; the fix is in PR #5192. > > On the patched build, the Java tests and the integration tests passed here. > The final binary-release step of that run produced no result, so I do not > have a clean full smoke pass. > > I am not claiming RC3 is broken for users; the hard-link failure in > particular may be specific to this host. > >> > AI-generated, human-reviewed. > > Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
