Add config option to disable incremental analysis #51
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
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.
This pull request adds an optional config option
incrementalAnalysistogobpie.json.If not specified, it defaults to
true, which is corresponds to the current behavior. If set tofalseit will run Goblint analysis with incremental analysis mostly* disabled.* As far as I know the
resetoption for theanalyzerequest does not disable incremental analysis but instead clears almost all existing incremental analysis results, which in practice has more or less the same effect as disabling incremental analysis.This is useful because incremental analysis in server mode can in some cases cause Goblint to crash or return inconsistent results (see for example goblint/analyzer#940).