A Brooks
A Brooks
Thanks, @humorless! for looking into it. I suspect our runners might have had a similar issue as you did on the 4G system—I think the JVM caps the heap size...
I still want to keep this issue open, since I'm not sure our tests should be creating so much garbage. However, I think the urgency is lessened with @humorless' change,...
I fell down a rabbit hole and wrote a little memory profiler plugin for Kaocha. Generated tests are creating quite a lot of garbage, as expected. ``` :lambdaisland.regal.spec-gen-test 4575.99MB (null)...
This doesn't seem to be causing CI issues after I pushed a fix (and we dropped Java 8/9 anyway), so this is a pretty low priority (and not a good...
I think it would be good to reduce Regal's memory usage in general or, if the problem is specific to how we're testing it, fix the tests so they don't...
Probably worth noting that Regal doesn't really have bespoke types that would use a lot of memory. It deals with forms (nested vectors), strings, and compiled regular expressions. So the...
Ultimately, I plan to close this since the main issue (failing CI runs) has been addressed.
I should also look at replacing `gen-carefully` with `such-that`, too.
A big issue here is that our generator seems to be generating characters that mess up a terminal, which makes it difficult to work with the output.
Hi @cons-dev, there's not a rush on this, but do you think you'll be able to work on this again soon?