Houston, did you make any progress on this? If this keeps happening, do we need to make our bats tests more robust in "checking" to see if a port is available first?
On 2024/06/12 05:45:08 David Smiley wrote: > Thanks for investigating. The nature of the failure would never occur in a > contained infrastructure. It’s sad to see having to deal with this. Do you > know if it’s even an option to run a particular job in a container? > Anyway, reach infra on Slack #askinfra > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Tue, Jun 11, 2024 at 6:42 PM Houston Putman <hous...@apache.org> wrote: > > > Currently the integration tests have been failing on Jenkins since around > > May 29th. It looks like there is a rogue process that has Auth enabled that > > is causing this problem. (Port 38603) > > > > For some reason a lot of the bin/solr commands choose to connect to this > > process instead of the SOLR_PORT that is in use by the integration tests at > > that point. I have a PR for making all commands in bin/solr use the same > > port defaulting, but that can really only land in 10.0. > > > > In the meantime we should see if infra can stop that rogue process so that > > the tests can start passing. > > > > - Houston > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
