[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. */
/* #undef HAVE_CLOCK_GETRES */

/* Define to 1 if you have the `clock_gettime' function. */
/* #undef HAVE_CLOCK_GETTIME */

/* Define to 1 if you have the `clock_settime' function. */
/* #undef HAVE_CLOCK_SETTIME */

/* Define if the C compiler supports computed gotos. */
/* #undef HAVE_COMPUTED_GOTOS */


When this happens, __PyTime_FromTimespec is undefined in pytime.c:747.
../Python/pytime.c:747:9: error: implicit declaration of function 
‘_PyTime_FromTimespec’; did 
you mean ‘_PyTime_FromTimeval’? [-Werror=implicit-function-declaration]
 if (_PyTime_FromTimespec(tp, &ts, raise) < 0)
 ^~~~
 _PyTime_FromTimeval
cc1: some warnings being treated as errors
make[2]: *** [Makefile:1553: Python/pytime.o] Error 1

--
components: Build
messages: 300238
nosy: pmatos
priority: normal
severity: normal
status: open
title: !HAVE_CLOCK_GETTIME causes problems with _PyTime_FromTimespec
type: compile error

___
Python tracker 
<http://bugs.python.org/issue31199>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[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 
<http://bugs.python.org/issue31199>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[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: Build
files: files.zip
messages: 300240
nosy: pmatos
priority: normal
severity: normal
status: open
title: address sanitizer build fails
type: compile error
Added file: http://bugs.python.org/file47081/files.zip

___
Python tracker 
<http://bugs.python.org/issue31200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[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 modules found by detect_modules() in setup.py, have been
built by the Makefile instead, as configured by the Setup files:
atexitpwd   time   

running build_scripts
copying and adjusting /home/pmatos/Projects/cpython/Tools/scripts/pydoc3 -> 
build/scripts-3.7
copying and adjusting /home/pmatos/Projects/cpython/Tools/scripts/idle3 -> 
build/scripts-3.7
copying and adjusting /home/pmatos/Projects/cpython/Tools/scripts/2to3 -> 
build/scripts-3.7
copying and adjusting /home/pmatos/Projects/cpython/Tools/scripts/pyvenv -> 
build/scripts-3.7
changing mode of build/scripts-3.7/pydoc3 from 664 to 775
changing mode of build/scripts-3.7/idle3 from 664 to 775
changing mode of build/scripts-3.7/2to3 from 664 to 775
changing mode of build/scripts-3.7/pyvenv from 664 to 775
renaming build/scripts-3.7/pydoc3 to build/scripts-3.7/pydoc3.7
renaming build/scripts-3.7/idle3 to build/scripts-3.7/idle3.7
renaming build/scripts-3.7/2to3 to build/scripts-3.7/2to3-3.7
renaming build/scripts-3.7/pyvenv to build/scripts-3.7/pyvenv-3.7
./python  ../Tools/scripts/run_tests.py -v test_that_failed
/home/pmatos/Projects/cpython/debug/python -u -W default -bb -E -W 
error::BytesWarning -m test -r -w -j 0 -u all,-largefile,-audio,-gui -v 
test_that_failed
== CPython 3.7.0a0 (heads/master:48d9823a0e, Aug 14 2017, 11:53:56) [GCC 7.1.1 
20170622 (Red Hat 7.1.1-3)]
== Linux-4.11.11-300.fc26.x86_64-x86_64-with-fedora-26-Twenty_Six little-endian
== hash algorithm: siphash24 64bit
== cwd: /home/pmatos/Projects/cpython/debug/build/test_python_22582
== CPU count: 16
== encodings: locale=UTF-8, FS=utf-8
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, 
dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=1, 
verbose=0, bytes_warning=2, quiet=0, hash_randomization=1, isolated=0)
Using random seed 8085058
Run tests in parallel using 18 child processes
0:00:00 load avg: 15.90 [1/1/1] test_that_failed failed
test test_that_failed crashed -- Traceback (most recent call last):
  File "/home/pmatos/Projects/cpython/Lib/test/libregrtest/runtest.py", line 
163, in runtest_inner
the_module = importlib.import_module(abstest)
  File "/home/pmatos/Projects/cpython/Lib/importlib/__init__.py", line 127, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 994, in _gcd_import
  File "", line 971, in _find_and_load
  File "", line 953, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'test.test_that_failed'

1 test failed:
test_that_failed
Re-running failed tests in verbose mode
Re-running test 'test_that_failed' in verbose mode
test test_that_failed crashed -- Traceback (most recent call last):
  File "/home/pmatos/Projects/cpython/Lib/test/libregrtest/runtest.py", line 
163, in runtest_inner
the_module = importlib.import_module(abstest)
  File "/home/pmatos/Projects/cpython/Lib/importlib/__init__.py", line 127, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 994, in _gcd_import
  File "", line 971, in _find_and_load
  File "", line 953, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'test.test_that_failed'

1 test failed again:
test_that_failed

Total duration: 355 ms
Tests result: FAILURE
make: *** [Makefile:1019: test] Error 2

--
components: Tests
messages: 300241
nosy: pmatos
priority: normal
severity: normal
status: open
title: module test that failed doesn't exist

___
Python tracker 
<http://bugs.python.org/issue31201>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[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 and ran only those. :)

--

___
Python tracker 
<http://bugs.python.org/issue31201>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com