Do not fail diff informed analyses when analyze is run twice in the same job #2876
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.
Tolerate the diff range extension pack directory already existing and overwrite it, to avoid failing in jobs that call
analyze
more than once.Also defer the computation of the dependency caching default cache config to avoid getting the value of the
RUNNER_TEMP
environment variable before it can be overridden by test logic.And finally disable diff-informed analyses within the config parsing tests, since these tests do not account for the additional query filter added by diff-informed analyses.
Merge / deployment checklist