[issue44728] Testsuite fails on x86_64

New submission from Erich Eckner : The following tests fails on x86 32 bit: test_cmath test_math test_posix test_turtle - looks, like the expected precision is too high. Full log is attached. -- components: Tests files: build-log.php?a=pentium4&p=python messages: 398084

[issue34095] segfault in testsuite

New submission from Erich Eckner : building python 2.7.15 on archlinux32 from source succeeds, but running the testsuite segfaults with: test_writelines (idlelib.idle_test.test_io.PseudeOutputFilesTest) ... /usr/bin/xvfb-run: line 181: 3617 Segmentation fault (core dumped) DISPLAY

[issue34096] testsuite fails assertion

New submission from Erich Eckner : building python 2.7.15 on archlinux32 (the i686 branch of archlinux) from source succeeds, but running the testsuite (with some segfaulting tests disabled - see issue34095) results in an assertion error: test_wrongsize (test.test_audioop.TestAudioop

[issue34096] [2.7] test_audioop.test_max() failed: AssertionError: -2147483648 != 2147483648L

Erich Eckner added the comment: yes, I'm using gcc (GCC) 8.1.1 20180531 I attached the created pythoninfo -- Added file: https://bugs.python.org/file47687/pythoninfo ___ Python tracker <https://bugs.python.org/is

[issue34096] [2.7] test_audioop.test_max() failed: AssertionError: -2147483648 != 2147483648L

Erich Eckner added the comment: yes, indeed, I just tested with your three flags-variables set and the build+test succeeded - I'll have to figure out what the minimal change is, though :-) -- ___ Python tracker <https://bugs.py

[issue34096] [2.7] test_audioop.test_max() failed: AssertionError: -2147483648 != 2147483648L

Erich Eckner added the comment: yes, you were absolutely right: just adding "-fwrapv" to $OPT is enough. Ok, is this something, we at archlinux32 need to opt in for, or is this something, that the configure script should a

[issue34095] [2.7] test_idle fails with: /usr/bin/xvfb-run: line 181: 3617 Segmentation fault

Erich Eckner added the comment: > Can you try to get the Python traceback and/or C traceback using gdb? Sry, I can't - I don't know how to use gdb :-( Is there some one-line command which makes gdb start xvfb-run and attach to it? Or do I need to start xvfb-run and separately att

[issue34095] [2.7] test_idle fails with: /usr/bin/xvfb-run: line 181: 3617 Segmentation fault

Erich Eckner added the comment: ok, some update: 1st: running the complete test suite with xvfb fails (as already reported): > LD_LIBRARY_PATH="${srcdir}/Python-${pkgver}":${LD_LIBRARY_PATH} \ xvfb-run "${srcdir}/Python-${pkgver}/python" -m test.regrtest -v -ua

[issue34096] [2.7] test_audioop.test_max() failed: AssertionError: -2147483648 != 2147483648L

Erich Eckner added the comment: ah, that would explain, why we don't get it set automatically on archlinux32 - there's "export OPT=$CFLAGS" right infront of ./configure ... - so $OPT is set and thus, -fwrapv is not appended -- __

[issue34095] [2.7] test_idle fails with: /usr/bin/xvfb-run: line 181: 3617 Segmentation fault

Erich Eckner added the comment: Yes, I get much further in the test suite, currently (40k lines logged vs. 23k). Now, it succeeds until: 0:08:26 load avg: 0.72 [358/403/3] test_tuple test_addmul (test.test_tuple.TupleTest) ... ok test_bigrepeat (test.test_tuple.TupleTest) ... /usr/bin/xvfb

[issue34095] [2.7] Seg fault on archlinux 32 when run tests with xvfb-run

Erich Eckner added the comment: yes, I'm also not sure what's different now - I executed the very same commands on the very same source tree :-/ -- ___ Python tracker <https://bugs.python.o