Remove unsat states from invokes #1071
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CaelmBleidd
force-pushed
the
caelmbleidd/error_with_wrappers_and_query
branch
from
08bb161 to
b46f461
Compare
CaelmBleidd
force-pushed
the
caelmbleidd/error_with_wrappers_and_query
branch
from
b46f461 to
a9ae8af
Compare
sergeypospelov
approved these changes
Oct 5, 2022
AbdullinAM
pushed a commit
to AbdullinAM/UTBotJava
that referenced
this pull request
Oct 17, 2022
AbdullinAM
pushed a commit
to AbdullinAM/UTBotJava
that referenced
this pull request
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When we process an invocation, we should resolve parameters for a call. During the resolve, our state might become UNSAT (how is it possible is another question).
Fixes #107
Type of Change
How Has This Been Tested?
Automated Testing
org.utbot.examples.collections.MapsPart1Test#testMapOperator
Manual Scenario
Run idea on the added method for auto testing and check it in plugin with 300s time limit. We should not have any errors
Checklist (remove irrelevant options):