Unexpected UNSAT status during parameters resolving

[CaelmBleidd]

Description

Because of some reason we got an UNSAT status for a state during parameters resolving in an invocation processing. It happens inside org.utbot.engine.Traverser#initStringLiteral method, but it is not clear, how it is possible to get unsat because of creating a new object.

To Reproduce

Steps to reproduce the behavior:

1. Run the 'UTBotTest' project in debug IntelliJ Idea
2. Set a breakpoint inside of the code that drops unsat states in commonInvokePart
3. Use plugin to generate tests for class MapOperate

Expected behavior

The breakpoint should never be reached.

Actual behavior

UTBot reaches the breakpoint.

Environment

There is no specific environment, but it might take a long time to reach it.

Additional context

There is no additional context.