I've had a RHEL/Rocky 9 PR for Dataverse documentation waiting for a while now, because it says that Dataverse will be tested on Rocky 9. I've had a Rocky 9 dataverse-ansible branch waiting for a while now, because on each run I get (different) IT failures. Same OpenJDK version, same Payara5, same develop branch, different underlying system libraries. Arguably, part of integration testing is to determine whether there might be versioning problems with said libraries, but... I'm not certain on the best way to proceed.
It would certainly be nice to be able to spin up Rocky 9 and run the full suite of API tests against it without it falling over.
If different IT tests are failing each time, is the JVM out of memory?
At a high level, I'd say we'd need to push this through our regular process. We should create an issue, probably put it in the "Dataverse Team" column, estimate it, etc. It's real work!
Should we create a base image based on Rocky 9 as well?
@Oliver Bertuch a Rocky 9 base image is an interesting thought. European installations seem to prefer Debian/Ubuntu; American installations often prefer RHEL/Rocky/family. If there is any discernable difference posed by underlying system libraries (and there may be), a Rocky 9 base image might not be a terrible thing to have.
Hey! Take the base image jibba jabba to #containers please! :heart:
@Philip Durbin it's all interdisciplinary.
@pdurbin though today it's AdminIT.testBannerMessages:838 expected:<[OK]> but was:<[ERROR] again. Not OoM killer or SELinux, I checked.
@Don Sizemore this topic seems as good a place as any to highlight which tests are failing on Rocky 9. Thanks!
@Philip Durbin what are your laptop 500s?
In Docker, on my laptop, I get these 500 errors when I try to run the whole API test suite: https://dataverse.zulipchat.com/#narrow/stream/375812-containers/topic/running.20API.20tests/near/345213679
Last updated: Nov 01 2025 at 14:11 UTC