Tests can be overly resource hungry or otherwise get out of control - add hardening somehow?

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"

DeprecationTest > testExample() STANDARD_ERROR
    Exception in thread "Chunk-Processing-Reactor" java.lang.OutOfMemoryError: GC overhead limit exceeded
    Exception in thread "Thread-148" java.lang.OutOfMemoryError: GC overhead limit exceeded

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Chunk-Processing-6"

Inizia dall’output della console Jenkins collegato per PR-29 e dal fallimento di DeprecationTest testExample(). Indaga sugli errori segnalati „GC overhead limit exceeded“ e determina se il test o la build necessitano di un rafforzamento delle risorse. Il lavoro è completato quando il test non esaurisce più la memoria né supera in altro modo i limiti di risorse previsti.