<div dir="ltr">Hi Sean,<div><br></div><div>I'm getting memory errors today using devstack. Never happened to me before with 8GB of RAM... </div><div><br></div><div>It seems the mirrors still have the version with the memory leak.</div><div><br></div><div>Thank you for the information, you saved my day!</div><div><br></div><div>Diego</div><img width="1" height="1" class="mailtrack-img" src="https://mailtrack.io/trace/mail/c0a8df3c222beec2e561438fc0662b50b36f2520.png"></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"> -- <br><span style="border-collapse:separate;font-family:Times"><span style="border-collapse:collapse;font-family:arial,sans-serif"><div align="left" style="font-size:13px"><div><font><span lang="ES" style="font-family:Arial">Diego Parrilla<br><a href="http://www.stackops.com/" title="file:///C:/Documents%20and%20Settings/carolina.capsir.per1/Application%20Data/Microsoft/Signatures/www.garrigues.com
www.garrigues.com" style="color:rgb(7,77,143)" target="_blank"><span title="file:///C:/Documents%20and%20Settings/carolina.capsir.per1/Application%20Data/Microsoft/Signatures/www.garrigues.com"></span></a></span></font><font face="Arial" style="font-family:arial,helvetica,sans-serif"><b>CEO</b><font size="1"><br></font></font><span style="border-collapse:separate;font-family:Times;font-size:medium"><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"></span></span><b><font face="Arial" style="font-family:arial,helvetica,sans-serif"><a href="http://www.stackops.com/" target="_blank"><b>www.stackops.com</b></a> | </font></b><font face="Arial" style="font-family:arial,helvetica,sans-serif"><font size="1"> <a href="mailto:diego.parrilla@stackops.com" target="_blank">diego.parrilla@stackops.com</a></font></font><span style="border-collapse:separate;font-family:Times;font-size:medium"><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><font color="#004438" face="Arial"><b><b><span lang="EN-GB" style="font-size:10pt"></span></b></b></font></span></span><font face="Arial" style="font-family:arial,helvetica,sans-serif"><font size="1"> | </font></font><span style="font-family:arial,helvetica,sans-serif;font-size:x-small">+34 91 005-2164 | </span><a style="font-size:x-small;font-family:arial,helvetica,sans-serif">skype:diegoparrilla</a></div></div><div style="font-size:13px"><font color="#004438" face="Arial"><b><p><span style="border-collapse:separate;color:rgb(0,0,0);font-family:Times;font-size:medium"><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><span style="border-collapse:separate;font-family:Times;font-size:medium"><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><font color="#004438" face="Arial"><b><b><span lang="EN-GB" style="font-size:10pt"><img src="http://stackops.s3-external-3.amazonaws.com/STACKOPSLOGO-ICON.png"></span></b></b></font></span></span></span></span></p></b></font></div></span></span><div><br></div></div></div>
<br><div class="gmail_quote">On Sat, Sep 27, 2014 at 3:27 PM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 09/27/2014 09:23 AM, Sean Dague wrote:<br>
> If anyone is checking in on their patches this weekend and sees that<br>
> they seem to be failing on really odd stuff, like docs, pep8, unit<br>
> tests... it looks like it's because setuptools 6.0 has a terrible memory<br>
> leak when processing requirements - I've filed it upstream<br>
> <a href="https://bitbucket.org/pypa/setuptools/issue/259/setuptools-60-causes-giant-memory-leaks-in" target="_blank">https://bitbucket.org/pypa/setuptools/issue/259/setuptools-60-causes-giant-memory-leaks-in</a><br>
><br>
> Setuptools 6.0 was released Friday night. (Side note: as a service to<br>
> others releasing major software bumps on critical python software on a<br>
> Friday night should be avoided.)<br>
><br>
> If anyone has a direct line to setuptools devs, please reach out. The<br>
> entire CI pipeline is basically dead until this is addressed.<br>
><br>
> Because of how deeply embedded setuptools is in our environment... there<br>
> isn't much we can do without an upstream fix.<br>
<br>
</span>Just as I sent this Jason R. Coombs said he pulled the release from<br>
pypi. No idea if that will automatically get pulled from our mirrors or<br>
not, but that should make things function again (see update in -<br>
<a href="https://bitbucket.org/pypa/setuptools/issue/259/setuptools-60-causes-giant-memory-leaks-in" target="_blank">https://bitbucket.org/pypa/setuptools/issue/259/setuptools-60-causes-giant-memory-leaks-in</a>)<br>
<div class="HOEnZb"><div class="h5"><br>
        -Sean<br>
<br>
--<br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>