Uh oh!
There was an error while loading. Please reload this page.
Disabling valgrind for now. - #3068
Conversation
rwgk
commented
Jul 10, 2021
Logging a fresh observation for future reference (thanks a lot to @Yhg1s for making this possible!): Google-internal testing with (ASAN, UBSAN) x (Python 3.9) x (fastbuild, opt, dbg) is clean BUT MSAN x (Python 3.9) x (fastbuild, opt, dbg) fails, pointing to the exact same line number in Objects/typeobject.c as valgrind. See below. This makes potential root causes 4. and 5. in the PR description very unlikely. Also note that test_class_sh_trampoline_shared_from_this.py is the only failing test. I had to exclude 5 tests that need numpy/scipy/eigen, but the rest runs clean with all sanitizers. For completeness, the 5 excluded tests are: test_buffers.py, test_eigen.py, test_numpy_array.py, test_numpy_dtypes.py, test_numpy_vectorize.py. |
* Using latest pytest main branch for 3.9 and 3.10. * WORKAROUND_ENABLING_ROLLBACK_OF_PR3068 in test_class_sh_trampoline_shared_from_this.py First experiment combining two potential fixes: latest pytest, workaround. If this succeeds the next step will be to try only latest pytest without the workaround. Note: the workaround is known to resolve the MSAN error reported under pybind#3068 (comment)
* Using latest pytest main branch for 3.9 and 3.10. * WORKAROUND_ENABLING_ROLLBACK_OF_PR3068 in test_class_sh_trampoline_shared_from_this.py First experiment combining two potential fixes: latest pytest, workaround. If this succeeds the next step will be to try only latest pytest without the workaround. Note: the workaround is known to resolve the MSAN error reported under pybind#3068 (comment)
* * Rollback of PR #3068. * Using latest pytest main branch for 3.9 and 3.10. * WORKAROUND_ENABLING_ROLLBACK_OF_PR3068 in test_class_sh_trampoline_shared_from_this.py First experiment combining two potential fixes: latest pytest, workaround. If this succeeds the next step will be to try only latest pytest without the workaround. Note: the workaround is known to resolve the MSAN error reported under #3068 (comment) * WORKAROUND_ENABLING_ROLLBACK_OF_PR3068 = False * Narrowing down WORKAROUND_ENABLING_ROLLBACK_OF_PR3068 to Python 3.9
EDIT 2020-07-10: This PR was rolled back with PR #3090.
Some observations:
The root cause for the error could be:
Based on the ASAN, MSAN, UBSAN testing, 1. and 2. do not seem to be the most likely root causes, although only proving what the root cause actually is can rule that out completely. Unfortunately this is likely to be very time consuming.