<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello everybody<br>
</p>
<p>Because of the changing add-on environment, we plan to switch off
Mozmill testing by the end of the year. Mozmill ran using a
bootstrapped extension (already hacked from a non-bootstrapped
extension) which no longer be feasible when we remove support for
bootstrapped extensions.<br>
</p>
<p>Shortly I'll be landing a patch which <i>copies</i> all Mozmill
tests to Mochitest (<a moz-do-not-send="true"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1599991">bug
1599991</a>). Some of them are switched off because they fail
reliably.<br>
</p>
<p>For a time both sets of tests will be running simultaneously, so
you will need to:</p>
<ul>
<li>run both sets of tests in your Try runs</li>
<li>if you break something, check it is fixed in both tests<br>
</li>
<li>modify both copies of a test if you make a modification</li>
<li>there may be some lingering orange on TreeHerder for a while –
if your Try run is orange and you don't know if you caused it,
ask<br>
</li>
</ul>
<p>The new tests will live under <tt>mail/test/browser</tt> with
similar names to the old tests in <tt>mail/test/mozmill</tt>. The
modules in <tt>mail/test/mozmill/shared-modules</tt> are used by
both sets of tests (ie. there's only one copy of these files).<br>
</p>
<p>Once we're satisfied the new tests are working okay, Mozmill will
be switched off forever and you can unlearn <tt>make -C
path/to/objdir mozmill-one SOLO_TEST=folder/test-name.js</tt>
:-)<tt></tt><tt></tt></p>
<p>GL</p>
<p>P.S. Mochitest debug runs come with leak checking turned on by
default. Some of the test runs leak over 100MB. This is not good!
Please help fix it if you have the know-how.<br>
</p>
</body>
</html>