Long test generation

[tosha63]

We decided to use your product in our project.
I previously tested it on a simple light project, that tests are created and everything is fine.
When you run it on the main project, the generation of tests takes a very long time (7-12 minutes) and when it ends, nothing happens and the test class is not created.
I don’t understand, what’s wrong?

[tyuldashev]

Hi,
Time for test generation depends on how many classes are under test. Default timeout is 60 seconds per class, so if you generate tests for ~10 or more classes, then 7-12 min looks reasonable.

Unfortunately without logs or samples from your project it's difficult to understand what exactly went wrong. You may try:

• run test generation on one class in your project, to understand if it work in that project
• run on some package with several classes, to localize problem to specific package/class
• look into log for errors or send it to us, it should be in temp folder C:\Users\xxxxx\AppData\Local\Temp\UTBot\rdEngineProcessLogs\utbot-engine-current.log

[tosha63]

I start generation on one class, one method. The class contains many dependencies, maybe because of this.

Logs below

18:49:12.224 | ERROR | CountingThreadPoolExecutor | Worker thread execution failed: Failed to apply jb to <classpath: java.lang.String toString()>
java.lang.RuntimeException: Failed to apply jb to <classpath: java.lang.String toString()>
	at soot.asm.AsmMethodSource.getBody(AsmMethodSource.java:2281) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.SootMethod.retrieveActiveBody(SootMethod.java:447) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.PackManager.lambda$retrieveAllBodies$2(PackManager.java:1250) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: java.lang.OutOfMemoryError: Java heap space
	at java.util.HashMap.resize(HashMap.java:702) ~[?:?]
	at java.util.HashMap.putVal(HashMap.java:627) ~[?:?]
	at java.util.HashMap.putMapEntries(HashMap.java:514) ~[?:?]
	at java.util.HashMap.<init>(HashMap.java:484) ~[?:?]
	at soot.jimple.toolkits.typing.fast.Typing.<init>(Typing.java:46) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.jimple.toolkits.typing.fast.DefaultTypingStrategy.createTyping(DefaultTypingStrategy.java:55) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.jimple.toolkits.typing.fast.TypeResolver.applyAssignmentConstraints(TypeResolver.java:483) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.jimple.toolkits.typing.fast.TypeResolver.inferTypes(TypeResolver.java:151) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.jimple.toolkits.typing.TypeAssigner.internalTransform(TypeAssigner.java:129) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.BodyTransformer.transform(BodyTransformer.java:47) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.Transform.apply(Transform.java:126) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.JimpleBodyPack.applyPhaseOptions(JimpleBodyPack.java:79) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.JimpleBodyPack.internalApply(JimpleBodyPack.java:112) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.Pack.apply(Pack.java:126) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.asm.AsmMethodSource.getBody(AsmMethodSource.java:2279) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.SootMethod.retrieveActiveBody(SootMethod.java:447) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.PackManager.lambda$retrieveAllBodies$2(PackManager.java:1250) ~[soot-utbot-fork-4.4.0-FORK-2.jar:?]
	at soot.PackManager$$Lambda$141/0x0000000800e90d38.run(Unknown Source) ~[?:?]
	... 3 more

[tyuldashev]

So the problem is lack of memory for some reason.

• How much memory is available on computer?
• Could you provide reproducer of the problem? That could be your project or artificial project with all dependencies but only with one that method, if it's reproducible there.

We never met such problem before and currently it's not possible to allocate more memory through configuration.

[tosha63]

RAM 40 GB.
I tried to increase the memory in the settings from 4GB first to 8GB (I got the same error) and then increased it to 16GB (I also got an error)
Unfortunately I cannot provide the project.

[tyuldashev]

UTBot starts additional process with default settings (1Gb most probably), so increasing memory in IDEA doesn't help.

[tosha63]

Do not quite understand. What should I do in this case?

[tyuldashev]

I've entered an issue to allow customization of memory allocation (#2664). Unfortunately that's all we can do right now, without ability to reproduce problem on our side.

[tosha63]

What settings can I edit in this file to make the test generation work?

[tyuldashev]

The entered case is to introduce setting to manage memory allocation. At the moment there is no such setting as we haven't met with such problem before.

Meanwhile you may try to use only Symbolic or Fuzzer generator or try to reduce generation timeout.

Try to set Fuzzing to 100% and Symbolic to 100%, maybe one of them would work.

[tosha63]

None of the above helped...