<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>This bug in bpo-33329:</p>
<blockquote>
<p><a class="moz-txt-link-freetext" href="https://bugs.python.org/issue33329">https://bugs.python.org/issue33329</a><br>
</p>
</blockquote>
<p>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
<i>nine hours ago</i> 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.</p>
<p>Obviously it'd be best if the folks involved with the original
PRs (Antoine?) took over. I'm sending this to a wider audience
just because I'd hoped to tag the next RCs for 3.4 and 3.5 this
weekend, and the original participants in this fix may not be
available, and I'm hoping I won't have to slip the schedule.<br>
</p>
<p><br>
</p>
<p>Thanks for your time,<br>
</p>
<p><br>
</p>
<p><i>/arry</i><br>
</p>
</body>
</html>