Judging from the API test failures at https://github.com/pdurbin/dataverse-api-test-runner/actions/runs/5715146690/job/15483847990 I suspect Solr might not be set up properly in GitHub Actions. Any ideas?
The log is full of errors like this:
org.apache.solr.client.solrj.SolrServerException: IOException occurred when talking to server at: http://solr:8983/solr/collection1
From https://github.com/pdurbin/dataverse-api-test-runner/suites/14567658790/artifacts/824866297
Philip Durbin said:
Judging from the API test failures at https://github.com/pdurbin/dataverse-api-test-runner/actions/runs/5715146690/job/15483847990 I suspect Solr might not be set up properly in GitHub Actions. Any ideas?
how does your docker-compose-payara6.yml differ from docker-compose-dev.yml in 8305-v3?
I do see a solr-initializer mounting conf at https://github.com/IQSS/dataverse/blob/8305-payara6-ee10-v3/docker-compose-dev.yml#L72 FWTW
Hmm. Good thought. I'm playing around with that here: https://github.com/pdurbin/dataverse-api-test-runner/commit/915a12c
It makes chown: /var/solr: No such file or directory go away.
This is the next error to fix, I think:
Executing /opt/docker-solr/scripts/precreate-core collection1 /template
cp: cannot stat '/template/': No such file or directory
@Don Sizemore I think you're on to something. I just pushed https://github.com/pdurbin/dataverse-api-test-runner/commit/4310c2c and the tests are getting farther.
I think that did it! Thanks, @Don Sizemore ! On develop anyway, I'm down to only three failing tests.
Last updated: Oct 30 2025 at 05:14 UTC