Open Cervator opened 4 years ago
I suspect it is not terminated engines during all tests run. Something with shutdowning. Every client engine takes 600MB+ by chunks (default view distance and server and client sides)
Yeah I tried to add more memory to the build agent but it still failed eventually. On the plus side we now have the watchful http://jenkins.terasology.io/teraorg/job/Utilities/job/BuildWatchinator/ which will find and terminate such stalled builds. So at least they won't stall forever anymore
Maybe mildly similar to #25 but distinct - in this case
testExample
literally went out of memory:http://jenkins.terasology.io/teraorg/job/Terasology/job/Modules/job/M/job/ModuleTestingEnvironment/job/PR-29/1/console
I'm not sure what the best way to address this is. It doesn't look like the build agent itself ran out of memory, it had a little more space allocated, although maybe if Java requested a large enough chunk of memory (more than 300MB in one reqest?) that could be related
Maybe it is something more specific? The build log talks about "GC overhead limit exceeded"