Timeout 0 ms on Problems view for a Successful symbolic execution

[alisevych]

Description

An error is shown on Problems view
Timeout 0 ms for phase StatisticsCollectionPhase elapsed, controller timeout - 2
for a successful test generated with Symbolic engine.

To Reproduce

1. Run the 'utbot' project in IntelliJ Idea 2022.2 Ultimate
2. Install the latest IU plugin built from main - take utbot-intellij-IU-2023.3.* artefact
3. Use plugin to generate tests for org/utbot/examples/mock/others package
   with default settings (Fuzzing/Symbolic) and Mock everything outside package and Do NOT mock static methods
4. Check errors detected by UnitTestBot on Problems view and SARIF-report for SideEffectApplier
5. Navigate to the generated test

Expected behavior

Errors are not expected for successful executions.
Or they should be considered as error-prone.

Actual behavior

The following error is shown on Problems view:
"Unexpected behavior: Timeout 0 ms for phase StatisticsCollectionPhase elapsed, controller timeout - 2.\nTest case: applySideEffect(<ExampleClass>)\nGenerated test for this case"

Visual proofs (screenshots, logs, images)

    ///region SYMBOLIC EXECUTION: SUCCESSFUL EXECUTIONS for method applySideEffect(org.utbot.examples.mock.service.impl.ExampleClass)

    /**
     * @utbot.classUnderTest {@link SideEffectApplier}
     * @utbot.methodUnderTest {@link SideEffectApplier#applySideEffect(ExampleClass)}
     */
    @Test
    @DisplayName("applySideEffect: ")
    public void testApplySideEffect() {
        SideEffectApplier sideEffectApplier = new SideEffectApplier();
        ExampleClass aMock = mock(ExampleClass.class);
        aMock.field = 1;

        sideEffectApplier.applySideEffect(aMock);

        int finalAMockField = aMock.field;

        assertEquals(2, finalAMockField);
    }
    ///endregion

SideEffectApplierReport.sarif

Environment

Windows 10 Pro
IntelliJ IDEA 2022.2.4 Ultimate
Gradle, JDK 11

Additional context

The following bug reproduced with this scenario simultaneously:

• UTBot generates several empty test classes when run for a pack of classes #1879