[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Shlomi Fish added the comment: Here is the new output of the make test with Python-3.4.1 : shlomif@telaviv1:~$ uname -a Linux telaviv1.shlomifish.org 3.15.6-desktop-1.mga5 #1 SMP Wed Jul 23 22:28:50 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux You may wish to install a Mageia Linux x86-64 Cauldron

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Mark Lawrence added the comment: Is this still a problem with later versions of Python on this platform? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18188

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

New submission from Shlomi Fish: After I build Python-3.3.2 from the .tar.xz using the following script (on Mageia Linux Cauldron x86-64): #!/bin/bash ./configure --prefix=$HOME/apps/python3 --with-threads \ --enable-ipv6 --with-dbmliborder=gdbm \

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

R. David Murray added the comment: This looks related to issue 14443, which was supposed to be fixed in 3.3.0. Can you do some of the same debugging that was done in that issue and see if it reveals any more about the problem? Also, I notice from that issue that Antoine was (is?) running

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Shlomi Fish added the comment: Hi, I don't understand the issue in questioned - it's too wordy and unclear. I don't know how to do the debugging in question - please guide me. I should note that after I do «unset PYTHONDONTWRITEBYTECODE» then all tests pass except for test_ftp.py, which

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Antoine Pitrou added the comment: I don't really use Mageia anymore, that said: I should note that after I do «unset PYTHONDONTWRITEBYTECODE» [snip] Yep, this is a long-lasting Mageia issue. See: https://qa.mandriva.com/show_bug.cgi?id=50484 https://bugs.mageia.org/show_bug.cgi?id=3348 You

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

R. David Murray added the comment: Benjamin fixed the ftp error message, one commit after the 3.3.2 tag. Not sure if that is enough to make the test pass, though. So, it sounds like 18142 should be closed as works for me? That is, the remaining test failures are do to the poor system

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Shlomi Fish added the comment: I see regarding test_ftp.py and the verbosity of the tests and the absence of bdist_rpm in the output - however, shouldn't the test suite handle the presence of the PYTHONDONTWRITEBYTECODE=1 flag better? (E.g: refuse to run the tests to begin with (with an

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

R. David Murray added the comment: Given that we introduced the flag to support read-only file systems, I think one can argue that the test suite should support running on one. However, the right thing to do would be to set up a buildbot where that was true so that it doesn't get re-broken