Ha! I created a ticket for this very problem before I saw this in my inbox. (Sorry.)

But as it says on ticket, not only does it happen (with rnv v. 1.7.8) on my local system, it happens when I test with a tiny schema and a tiny file.

How do we throw more memory at rnv? It is a compiled C program. (Although it “uses Expat”, so could the problem be there?)
Answer: if we pass rnv the -s switch it “uses less memory and runs slower”.


Today, my Jenkins started to fail on the TEIP5-Test-dev build with an
out-of-memory error when running RNV, which I can also reproduce on my
desktop:

...
java -jar ../Utilities/lib/trang.jar testplus.rng testplus.rnc
xmllint --noent --dropdtd  testplus.xml | rnv testplus.rnc
stdin:1:0: error: out of memory
error: invalid input
make[1]: *** [Makefile:78: testplus.special] Error 1
make[1]: Leaving directory '/home/mholmes/tei/TEI/P5/Test'
make: *** [Makefile:195: test] Error 2

The failure is on line 78 of the Test/Makefile, and it's when
testplus.xml is processed through xmllint and passed to rnv for
validation against its matching rnc file.

It looks like Peter's Jenkins is not suffering from this, while Raff's
has not run the job since last August, so something else is problematic
there.

Can those of you who run the docker instance try running the tests and
see what you get? I suspect that the testplus.xml file has just somehow
edged over a size threshold and we can work around it by throwing a bit
of memory at xmllint or at rnv, but I'd like to get a bit more info first.