On Sat, Mar 2, 2019 at 7:08 AM Larry Hastings <la...@hastings.org> wrote:
> > This bug in bpo-33329: > > https://bugs.python.org/issue33329 > > was fixed for 3.6+, but it also affects 3.4 and 3.5. The bug is that with > newer versions of glibc--which I'm pretty sure has shipped on all major > Linux distros by now--the test suite may send signals that are invalid > somehow. As a result the test suite... blocks forever? I think? Anyway > the observed resulting behavior is that there are three regression tests in > each branch that seemingly never complete. I started the 3.4 regression > test suite *nine hours ago* and it still claims to be running--and the > 3.5 test suite isn't far behind. Technically, no, it's not a security > bug. But I simply can't ship 3.4 and 3.5 in this sorry state. > This is also potentially affecting PGO builds of 2.7 on Debian Buster with GCC. Somehow building with Clang is fine. Does the configure time choice of compiler make a difference here for 3.4 and 3.5? -- Joni Orponen
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
