New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detected non-deterministic results when --jobs is not set to 1 #1819
Comments
Hello Infer team, I'm following up on this issue and would greatly appreciate any insights you could provide. Thank you! |
Hi, it is indeed a known issue. Several fixes have landed on master since the 1.1 release (we ought to do one soon), so I would suggest:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I have recently been using Infer for an empirical study to detect non-deterministic behaviors in static analyzers. The experiments resulted in discovering some nondeterministic analysis results across multiple runs under various configurations of Infer.
v1.1.0
.ubuntu:20.04
and I am using Docker.infer --compilation-database compile_commands.json
with following checkers on--annotation-reachability --bufferoverrun --cost --loop-hoisting --pulse
, as well as these options used--dump-duplicate-symbols --headers --max-nesting --jobs --reactive --scheduler
.--jobs
option is not set to 1.For example, here are some different results from the running Infer under the same configuration
--headers --max-nesting 1 --jobs 5 --reactive --scheduler callgraph
.result 1:
result 2:
result 3:
Could you please offer some insights into this issue and suggest ways to mitigate the non-deterministic behavior when running Infer with multiple jobs? Thank you.
The text was updated successfully, but these errors were encountered: