Nathan Goldbaum
Nathan Goldbaum
I might try running the cramjam tests under ASAN and TSAN to see if it spots any issues.
I don't see any issues running the cramjam tests under ASAN on my mac. Here's the change I made to the makefile to set that up: ``` diff --git a/Makefile...
I don't see any ASAN issues running with `xdist` either.
I forgot to mention for anyone who wants to do this at home, you can install numpy with address sanitizer using this incantation in a numpy checkout: ``` python -m...
I didn't see any issues under TSAN either. I've also been unable to trigger these failures on my Mac or Ubuntu dev setup. @musicinmybrain is there a way I can...
Hmm, I'm still not able to reproduce the failure in a fedora 41 docker image. Did you use a virtualenv to install cramjam's dependencies? If not can you show me...
Read the above discussion more closely and tried the incantation from https://github.com/milesgranger/cramjam/issues/201#issuecomment-2635023986 to trigger it in fedora image and no dice.
I opened a Hypothesis issue, maybe of the maintainers will have a clue how to deal with the error https://github.com/HypothesisWorks/hypothesis/issues/4267. For now I pushed a commit to #200 that pins...
It looks like if I pass `--assert='plain'` to pytest I can bypass the crash. See #224.
Hmm, something is still funky with the anaconda build. I'm not sure how it was working before without including a C compiler in the recipe.