Hi all, has anyone else noticed the tests getting killed by a segmentation fault at the very end? It's a silent segmentation fault for me, and the only reason I noticed it to begin with is the buildbots, which rightly flag it.
Just to be explicit, I see: """ ... Index files saved. ---------------------------------------------------------------------- Ran 13 tests in 7.826s OK INFO runtest.run: =========================================================== INFO runtest.run: 276 tests passed, 0 tests failed, 2 tests skipped; 278 total """ but with a non-zero exit code -- this turns out to be because of a segmentation fault signal. It occurs randomly, in over half of the runtest runs I execute on my development machine, across all versions of python. I did re-create the pygr dir and re-build pygr each time, although I doubt that's important. It'd be nice to get some verification from someone that this is happening on their machine, too, before I spend time looking to pygr and pyrex. If someone could just run the pygr tests 10 times and check the exit values, that'd be great... thanks, --titus p.s. I haven't seen it on Mac OS X, just on Linux. -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
