Test generation timeout is exceeded 15 sec - 1 min for every run

[alisevych]

Description

Test generation timeout is exceeded 15 sec approximately for every UTBot run.

To Reproduce

1. Run the 'UTBotJava' project in IntelliJ Idea 2022.1.4
2. Install one of the latest from main branch
3. Open test generation dialog for utbot-sample/src/main/java/org/utbot/examples/algorithms/ArraysQuickSort.java for example
4. Set test generation timeout to 20 sec.
5. Check when test generation finishes.

Expected behavior

Tests are supposed to be generated during the defined timeout of 20 sec.

Actual behavior

Tests are generation for about 30-35 sec. (on the exact PC)

Environment

Windows 10 Pro
RAM 32.0 GB
Processor Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz
IntelliJ IDEA 2022.1.4
Heap memory allocated for IDEA is 2 GB

Additional context

If test generation timeout is set to 60 sec, test generation continues for 75 sec approx.

As discussed with @sergeypospelov and @Markoutte :
Summaries generation and Code generation is not taken into account.
Though currently some of them seems to take much time.
Investigation is needed.

[alisevych]

Reproducing on one of the latest builds from main - unit-test-bot/rc10102022

ArraysQuickSort

Test generation timeout was set to 20 sec. Progress-bar was running up to the end during 20 sec.
Then after 15-17 seconds the test class was created.

ArrayCastExample

Test generation timeout was set to 60 sec. Progress-bar was running up to the end during 20 sec.
Then after 15 seconds the test class was created.

Heap

Test generation timeout was set to 20 sec. Progress-bar was running up to the end during 20 sec.
Then after 50-55 seconds more the test class is created. Checked twice.

[alisevych]

For testability:
it would be great to add info log records for different phases of UnitTestBot test generation.

• Test generation initiated
• Collecting information (classes)
• Fuzzing phase
• Symbolic analysis phase
• Minimization
• Summaries
• Code generation

[alisevych]

The issue was fixed by #1151
Verified it on build from the latest main.