<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 26/11/2015 13:56, Mark Banner wrote:<br>
<blockquote cite="mid:56570F88.7070605@mozilla.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
At the moment, we have a nag monitor in place, that tells us
within a few hours of landing if something has caused a
regression. Getting infra of some form would good for all of
Mozilla.<br>
</blockquote>
Gijs asked me to expand on this... its basically a cron job running
on one of the AWS boxes we have for Hello (for testing the web UI
side), every few hours it pulls latest fx-team, runs eslint on the
loop directory.<br>
<br>
If there's output, its automatically emailed to a list, which is the
whole of the Hello dev team. In the odd instance where we've broken
it, normally the person who caused it has fixed it soon after.<br>
<br>
One of the things we do have on Hello, is a "run-all-loop-tests.sh"
script, this lets us run all tests we know are relevant (xpcshell,
mochitest, marionette, eslint), and so we're used to running that
before landing. Hence this has kept the failures down (alongside the
in-editor tools).<br>
<br>
Mark.<br>
</body>
</html>