Discussed in #593
Originally posted by cehteh January 23, 2026
Not actually about the RAM prices ;)
I have the situation that some mutations creating memory leaks (replacing - with + etc). This should be expected and normal in mutation testing. Such test should be just aborted before the OOM kills the test. Currently I fix this with a reasonable 'ulimit' for the shell running cargo mutants. The unintentional consequence here is that the whole mutation/build process is memory constrained which means I have to give it more memory than necessary not to kill the build. Ideally one should be able to limit the memory of the actual test run only.
Discussed in #593
Originally posted by cehteh January 23, 2026
Not actually about the RAM prices ;)
I have the situation that some mutations creating memory leaks (replacing - with + etc). This should be expected and normal in mutation testing. Such test should be just aborted before the OOM kills the test. Currently I fix this with a reasonable 'ulimit' for the shell running cargo mutants. The unintentional consequence here is that the whole mutation/build process is memory constrained which means I have to give it more memory than necessary not to kill the build. Ideally one should be able to limit the memory of the actual test run only.