[issue31201] module test that failed doesn't exist

2017-08-14 Thread Paulo Matos
Paulo Matos added the comment: Argh, apologies David. I hadn't noticed the mistake. I simply copy/pasted and was expecting the command line to rerun all the tests that had previously failed. I was assuming the suite had some kind of state that recorded the tests that previously failed an

[issue31201] module test that failed doesn't exist

2017-08-14 Thread Paulo Matos
New submission from Paulo Matos: Trying to rerun the tests that failed but it just says that the module doesn't exist. I am running the exact command line mentioned in the readme file: $ make test TESTOPTS="-v test_that_failed" running build running build_ext The following m

[issue31200] address sanitizer build fails

2017-08-14 Thread Paulo Matos
New submission from Paulo Matos: Build with address sanitizer fails miserably. Configuration in Fedora 26. I attach config.log and the output of $ ../configure --with-assertions --with-lto --with-pydebug --with-address-sanitizer --disable-ipv6 $ make -j18 profile-opt -- components

[issue31199] !HAVE_CLOCK_GETTIME causes problems with _PyTime_FromTimespec

2017-08-14 Thread Paulo Matos
Paulo Matos added the comment: OK, the problem was the missing libasan which made quite a few checks fail. We should check for libasan before all other checks, when compiling with --with-address-sanitizer. -- ___ Python tracker <h

[issue31199] !HAVE_CLOCK_GETTIME causes problems with _PyTime_FromTimespec

2017-08-14 Thread Paulo Matos
New submission from Paulo Matos: On a Fedora 26 system, I run configure as: $ ../configure --with-assertions --with-lto --with-pydebug --with-address-sanitizer --disable-ipv6 My pyconfig.h contains: /* #undef HAVE_CLOCK */ /* Define to 1 if you have the `clock_getres' function. */ /* #