You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
c-analyzer: bump MAX_SIZES for Modules/clinic/_testclinic.c.h #148775
make check-c-globals fails on main because Modules/clinic/_testclinic.c.h has outgrown its MAX_SIZES limit (120_000) in Tools/c-analyzer/cpython/_parser.py.
RuntimeError:
too much text, try to increase MAX_SIZES[MAXTEXT] in cpython/_parser.py
/…/Modules/clinic/_testclinic.c.h starting at line 288 to 4597
has code with length 120058 greater than 120000
The file is auto-generated by Argument Clinic and has grown since the limit was last set in 99e2c5e. Suggest bumping to 200_000.
I ran make check-c-globals on the current main branch (at commit ba0aca3), it ran successfully:
$ make check-c-globals
python3.15 ./Tools/c-analyzer/check-c-globals.py \
--format summary \
--traceback
(...)
checking analysis results...
-------------------------
total failures: 0
done checking
Categorized by storage:
@ashm-dev: Can you still reproduce the issue on the current main branch?
I'm curious that you're seeing an error since make check-c-globals is run as part of your pre-commit CI, in the "Check if generated files are up to date" job:
.github/workflows/build.yml: run: make check-c-globals
Activity
pythongh-148775: Bump c-analyzer MAX_SIZES for Modules/clinic/_testcl…
pythongh-148775: Bump c-analyzer MAX_SIZES for Modules/clinic/_testcl…
vstinner commentedon May 19, 2026
I ran
make check-c-globalson the current main branch (at commit ba0aca3), it ran successfully:@ashm-dev: Can you still reproduce the issue on the current main branch?
I'm curious that you're seeing an error since
make check-c-globalsis run as part of your pre-commit CI, in the "Check if generated files are up to date" job:vstinner commentedon May 25, 2026
Since
make check-c-globalsjust works, there is no need to change it. I close the issue: #148776 (comment).