[MSVC][ASAN] Cpython failed to run test_call test_functools tests with ASAN using MSVC on windows
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Hi,
Cpython failed to run test_call test_functools tests with ASAN using MSVC on windows, it can be reproduced on 151d1bf commit on main branch. Could you please help look at this issue? Thanks in advance.
Steps to reproduce the behavior:
- git clone https://github.com/python/cpython
- Open VS2022 x64 CMD & set CL= /fsanitize=address /GS- /wd5072 & set LINK= /InferASanLibs /incremental:no /debug
- cd /d C:\gitP\python\cpython\PCBuild
- get_externals.bat --clean-only
- build -e -p x64 -r --no-tkinter -v "/p:PlatformToolset=v143" "/p:WindowsTargetPlatformVersion=10.0.26100.0"
- rt -p x64 -q -x test_asyncio test_distutils test_importlib test_peg_generator test_tools test_socket test_compileall test_int test_sys test_venv test_embed test_urllib2net test_capi test_userdict
ErrorMessage:
For test_call:
- python.exe -u -W default -bb -E -m test --fast-ci -q test_call --dont-add-python-opts
Using random seed: 567836749
0:00:00 Run 1 test in parallel using 1 worker process (timeout: 10 min, worker timeout: 15 min)
…
test_varargs_keywords (test.test_call.TestCallingConventionsInstance.test_varargs_keywords) ... ok
test_varargs_key
1 test failed again:
test_call
== Tests result: FAILURE then FAILURE ==
10 slowest tests:
1 re-run test:
test_call
1 test failed:
test_call
Total duration: 3.7 sec
Total tests: run=0
Total test files: run=2/1 failed=1 rerun=1
Result: FAILURE then FAILURE
For test_functools
- python.exe -u -W default -bb -E -m test --fast-ci -q test_functools --dont-add-python-opts
Using random seed: 2525602501
0:00:00 Run 1 test in parallel using 1 worker process (timeout: 10 min, worker timeout: 15 min)
test_cache (test.test_functools.TestCacheC.test_cache) ... ok
...
File "C:\gitP\python\linkrepro\test\test_functools.py", line 2088 in fib
=================================================================
==7220==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc04c2ea82 (pc 0x7ffc04c2ea82 bp 0x0083a26041b0 sp 0x0083a2604000 T0)
SUMMARY: AddressSanitizer: stack-overflow
== Tests result: FAILURE ==
10 slowest tests:
1 test failed:
test_functools
0:00:01 Re-running 1 failed tests in verbose mode in subprocesses
0:00:01 Run 1 test in parallel using 1 worker process (timeout: 10 min, worker timeout: 15 min)
Re-running test_functools in verbose mode
test_lru_recursion (test.test_functools.TestLRUC.test_lru_recursion) ... Windows fatal exception: stack overflow
...
File "C:\gitP\python\linkrepro\test\test_functools.py", line 2088 in fib
=================================================================
==2268==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc04ca47f7 (pc 0x7ffc04ca47f7 bp 0x007b59a04320 sp 0x007b59a042a8 T0)
SUMMARY: AddressSanitizer: stack-overflow
==2268==ABORTING
1 test failed again:
test_functools
== Tests result: FAILURE then FAILURE ==
10 slowest tests:
1 re-run test:
test_functools
1 test failed:
test_functools
Total duration: 2.2 sec
Total tests: run=0
Total test files: run=2/1 failed=1 rerun=1
Result: FAILURE then FAILURE
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failures from the listed PCBuild commands using the MSVC ASAN configuration, starting with test_call and test_functools. Inspect test/test_functools.py around line 2088 and the failing test output to determine the scope of the stack-overflow behavior. Done means the affected tests pass reliably under this configuration without the reported ASAN failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100