<div dir="ltr"><div>I wanted to post an update. We are very close to achieving all green tests on browser-chrome (tracking in bug 1057512)- there are 3 bugs remaining:<br><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=525284"><b>Bug 525284</b></a> -<span id="summary_alias_container">
<span id="short_desc_nonedit_display">browser_bug400731.js is fragile, not always passing<br>** patch for review, should be resolved this week</span></span><br><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=963075"><b>Bug 963075</b></a> -<span id="summary_alias_container">
<span id="short_desc_nonedit_display">browser_pdfjs_[main|views].js leaks until shutdown when run as a standalone directory</span></span><br></div>** ttaubert found a root cause (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1058695"><b>Bug 1058695</b></a> -<span id="summary_alias_container">
<span id="short_desc_nonedit_display">Promises can keep a page alive and even prevent Firefox from shutting down)<br></span></span><div><div><div><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1041594"><b>Bug 1041594</b></a> -<span id="summary_alias_container">
<span id="short_desc_nonedit_display">browser_mozAudioChannel_muted.js crashes when run as a directory instead of a full suite<br>** initial patch, would like to know priority of this as it requires a bit more work<br>
<br></span></span></div><div><span id="summary_alias_container"><span id="short_desc_nonedit_display">We are really close to green, can we ensure Bug 1058695 and bug 1041594 have owners and a reasonably normal priority so we can finish this project? If this is unrealistic, we could discuss temporarily disabling the tests until there is time to fix the issues.<br>
<br></span></span></div><div><span id="summary_alias_container"><span id="short_desc_nonedit_display">Thanks again for all the work so far on this.<br><br></span></span></div><div><span id="summary_alias_container"><span id="short_desc_nonedit_display">-jmaher<br>
<br></span></span></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 19, 2014 at 3:08 PM, Gavin Sharp <span dir="ltr"><<a href="mailto:gavin@gavinsharp.com" target="_blank">gavin@gavinsharp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Aug 19, 2014 at 9:06 AM, Ed Morley <<a href="mailto:emorley@mozilla.com">emorley@mozilla.com</a>> wrote:<br>
> Agreed that this case is possibly slightly different - however this change<br>
> is merely exposing already flaky tests - and this change is very much<br>
> overdue. If the tests mentioned are really that important, then could we<br>
> please get people allocated to fixing them?<br>
<br>
We have allocated people to fixing them. These bugs were explicitly<br>
assigned in the 34.2 iteration:<br>
Bug 947574<br>
Bug 1002439<br>
Bug 1041537<br>
<br>
and we've made some significant progress in tracking them down. But as<br>
you know, fixing these issues can be relatively difficult.<br>
<br>
> Ultimately no one individual test should have the right to destroy the SnR<br>
> for a suite - and if we don't have this policy as a rapid (and enforceable<br>
> in practice) means to control rogue tests, then the only other hammer the<br>
> sheriffs have is to hide entire suites.<br>
<br>
If we're reduced to interacting with each other with hammers, then<br>
we've failed. Firefox peers will not ignore needinfo or review<br>
requests. If you feel that they are, then you can escalate to me as<br>
module owner. I do not ignore requests, and am quite responsive to<br>
email and IRC pings.<br>
<span class="HOEnZb"><font color="#888888"><br>
Gavin<br>
</font></span></blockquote></div><br></div>