Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

infer analyzer does not work with --jobs

Open Beginner friendly
#5,110 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start in codechecker_analyzer/analyzers/infer/analyzer.py, the file named in the issue’s workaround, and inspect how the Infer command is assembled when CodeChecker runs with --jobs. Compare the generated command with the workaround and run the reproduction using --jobs 1 and a larger job count. Done means Infer’s subprocesses no longer cause the overall process count to substantially exceed the requested jobs.

Written by the indexing model from the issue text.

Description

Describe the bug
When starting CodeChecker analyze with --jobs then most analyzers start only one process per slot. But infer itself starts a lot of sub-processes. So in the end much more processes than indicated by --jobs are running.
Starting infer with --jobs 1 fixes the issue.

CodeChecker version
6.29.1

To Reproduce
Steps to reproduce the behaviour:

Start CodeChecker analyze --jobs $(nproc) --analyzers infer -- compile_commands.json on a big build with many files.
Load goes much higher than $(nproc) since there are more infer processes than allowed by --jobs.

Expected behaviour
Load stays at $(nproc) or slightly above.

Additional context
infer 1.3.0

The following "patch" fixes the issue for me:

sed -i -e "s/--keep-going',/--keep-going', '--jobs', '1',/" codechecker_analyzer/analyzers/infer/analyzer.py
Dominant language
Python
Stars
2.6k
Forks
494
Avg merge
3d 1h
Merged PRs (30d)
20

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Ericsson/codechecker

All issues in Ericsson/codechecker

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.