[
https://issues.apache.org/jira/browse/SOLR-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834267#comment-15834267
]
Ishan Chattopadhyaya commented on SOLR-8581:
--------------------------------------------
bq. Looking into why this could've happened. Perhaps the test suite didn't
properly place all the libs/jars in the right places?
That was indeed the case; {{server/lib}} also needs to be copied. Fixed it with
this commit [0]. 6.3.0 -> 6.4.0 passes fine now.
For these integration tests, I think we should add more tests and have it work
against git branch/commit (instead of only released versions). After these, we
should run this once every release.
[0] -
https://github.com/viveknarang/solr-upgrade-tests/commit/29bc75e4dea4fc330227f3e079b9be89db7ca872
> Integration tests for rolling upgrades
> ---------------------------------------
>
> Key: SOLR-8581
> URL: https://issues.apache.org/jira/browse/SOLR-8581
> Project: Solr
> Issue Type: Test
> Reporter: Vivek Narang
>
> I intend to work on an integration test suite for Solr, to test for issues to
> deal with back compat, rolling upgrades etc.
> The interface for the test suite, as I'm planning, would be to have it accept
> two versions of Solr (either released versions or trunk/branch).
> I work on SolrCloud, and we need something like this to enable us to upgrade
> more frequently. I had a conversation with @Ishan Chattopadhyaya, who
> emphasised to me the need to have something like this.
> If there's already any ongoing effort in doing this, I can help out there.
> Please let me know.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
