disable loading of metadata blocks in API tests, more sleep

[pdurbin]

What this PR does / why we need it:

We can't ship 6.0 with failing tests.

Which issue(s) this PR closes:

• Closes DataversesIT.testMoveDataverse, DataversesIT.testImportDDI, FilesIT.testAccessFacet (again) #9868

Special notes for your reviewer:

During the containerization meeting yesterday we talked about why tests are failing at https://github.com/gdcc/api-test-runner . (This was about 20 minutes in at https://harvard.zoom.us/rec/share/Nsm8SZgE05wuziNoGPA9fYNCPoYH1sKqvgS7omn-nclo6qFTsAn-qu-pqF4JnFuZ.joqMRTV6SqSf5gMl ). One avenue to explore is how we load metadata blocks (added in PR #6921) but don't update the Solr schema. Is this a problem?

I disabled two tests with this note: Disabled because once there are new fields in the database that Solr doesn't know about, dataset creation could be prevented, or at least subsequent search operations could fail because the dataset can't be indexed.

It's somewhat mysterious why GitHub Actions is more sensitive to the loading of a metadata block than Jenkins is. Jenkins can be fixed with more sleep in #9874.

See test results below.

Suggestions on how to test this:

Check Jenkins and GitHub Actions.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No.

Is there a release notes update needed for this change?:

No.

Additional documentation:

None.

[pdurbin]

Results: run 1 as of ea333c9

Jenkins: https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-9873/1/display/redirect

• passed: https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-9873/1/testReport/

GitHub Actions: https://github.com/gdcc/api-test-runner/actions/runs/6050329427

• failed with one failing test (MoveIT.testMoveLinkedDataset:311 expected: <0> but was: <1>): https://github.com/gdcc/api-test-runner/actions/runs/6050329427/job/16419430764

[pdurbin]

Results: run 2 as of ea333c9 and 4139f70

Jenkins: https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-9873/2/display/redirect

• passed: https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-9873/2/testReport/

GitHub Actions: https://github.com/gdcc/api-test-runner/actions/runs/6052363698

• passed: https://github.com/gdcc/api-test-runner/actions/runs/6052363698

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:9868-disable-load-blocks

ghcr.io/gdcc/configbaker:9868-disable-load-blocks

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[donsizemore]

@pdurbin this doesn't look related? I just tested your branch on Rocky 9, and got:
[ERROR] HarvestingServerIT.testMultiRecordOaiSet:609 Wrong number of items on the first ListIdentifiers page ==> expected: <2> but was: <5>"

[pdurbin]

@donsizemore that one is a known issue:

• Update "Getting Set Up to Run REST Assured Tests" #9738

Over at https://github.com/gdcc/api-test-runner/blob/5e0f34127c1119cbd80148f1ec32ad561d6fca94/docker-compose-develop.yml I use this to get that test to pass:

  # to get HarvestingServerIT to pass
  - dataverse_oai_server_maxidentifiers=2
  - dataverse_oai_server_maxrecords=2

In dataverse-ansible we do something similar: https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible/blob/b409c6aa9aa4a29c1e9660a221f19f06adca8338/tasks/dataverse-optional-settings.yml#L23

[sekmiller]

Ok. the only two tests that use the deprecated load metadata block util have been disabled.
Any thoughts on when they might be returned?

[pdurbin]

I'd like to pick @poikilotherm's brain about why they seem to have an effect in Docker in particular, and apparently only after the Solr or JUnit upgrades. Still a mystery, I'm afraid. 😅