<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><a class="moz-txt-link-freetext" href="https://code.launchpad.net/~alan-griffiths/mir/fix-fd-leak-thomi-reported/+merge/168012">https://code.launchpad.net/~alan-griffiths/mir/fix-fd-leak-thomi-reported/+merge/168012</a><br>
<br>
On 07/06/13 09:26, Alan Griffiths wrote:<br>
</div>
<blockquote cite="mid:51B19948.4020109@canonical.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I'll look into this. (Is there a bug
registered?)<br>
<br>
On 07/06/13 04:20, Thomi Richards wrote:<br>
</div>
<blockquote
cite="mid:CAFkWetnLe_k6-CHVRq4cdM_QQQ+89tj38WqmQooTxr7xU-ZWow@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Hi,<br>
<br>
</div>
The mir_stress binary is now built as part of the
regular trunk build process. However, the client API
seems to be leaking FDs again.<br>
<br>
</div>
My plan is to make the stress tests run as part of every
merge proposal, which will make regressions such as this
impossible to land in the future. However, there's a bit
of infrastructure we need to wrangle until that can
happen, and I'm on holiday for the next few weeks.<br>
<br>
</div>
It would be great if someone familiar with the client API
could run the mir-stress tests (run "mir_stress -n 10"), fix
the FD leak, and possibly keep an eye on the situation until
we manage to get this automated.<br>
<br>
</div>
Cheers,<br clear="all">
<div>
<div>
<div>
<div>
<div><br>
-- <br>
<div dir="ltr">
<div>Thomi Richards<br>
</div>
<a moz-do-not-send="true"
href="mailto:thomi.richards@canonical.com"
target="_blank">thomi.richards@canonical.com</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>