Change unsafe access to jClass in updateGenericTypeInfo #1526
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
In
org.utbot.engine.Traverser#updateGenericTypeInfo
we accessexecutable
for the method under test. It goes intojClass
and extracts a method instance from it, which may cause an error if we don't have this class in the classpath. Since this function is not mandatory for analysis, we can just not update generic info and continue analysis instead of falling.Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Regression and integration tests
There are no additional tests since they highly depend on classpath, project configuration, soot transformation and other options. Unfortunately, the exact combination of these options is lost and the problem occurred on a project with closed code.
Automated Testing
There are no additional automatic tests.
Manual Scenario
There are no manual scenarios.
Checklist: