<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 3 January 2013 16:37, David Blaikie <span dir="ltr"><<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">My only hesitation here is that using LNT as the authoritative runner<br></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
does have a little more setup overhead for people wishing to run the<br>
suite (they need to install some extra stuff).<br></blockquote><div><br></div><div style>Yes, there is an issue on shared machines, regarding installing new software (mainly the virtualenv, since lnt itself is local to the sandbox).</div>
<div style><br></div><div style>However, to be fair, I found it way simpler to run the LNT tests than the buildbots. The documentation was much clearer and the process sleeker.</div><div><br></div><div style>cheers,</div>
<div style>--renato</div></div></div></div>