[
https://issues.apache.org/jira/browse/SOLR-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768093#comment-17768093
]
Houston Putman commented on SOLR-16979:
---------------------------------------
Just figured out another bin/solr command that tries to find a running Solr
process instead of using SOLR_PORT. "solr auth". It also doesn't support -p...
What a weird strategy for it.
We really need to have a unified way of specifying port (-p, then the only
running Solr process, then SOLR_PORT as a default) across all bin/solr commands.
This is causing the integration tests to fail when there are other processes
running on the machine.
> Randomize ports in BATS tests
> -----------------------------
>
> Key: SOLR-16979
> URL: https://issues.apache.org/jira/browse/SOLR-16979
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Integration Tests
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: 9.4
>
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> Currently all BATS tests run solr on port 8983. This means only one test can
> run at a time, and there is greater risk for port conflict on CI environments.
> Introduce random port assignment. Can be done by setting SOLR_PORT
> env.variable in build.gradle. And perhaps also setting a SOLR2_PORT variable
> for those tests that explicitly starts a second instance.
> Also, at the end of tests, try to assert that no process is still running,
> and properly clean up.
> Ref discussion in dev@
> https://lists.apache.org/thread/j9t29wx8zg9oj6xy9tnn8cq063nrp6yp
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
