<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 8, 2014 at 6:01 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">><br>
> On 24 December 2013 01:09, Philip Balister <<a href="mailto:philip@balister.org">philip@balister.org</a>> wrote:<br>
> >> 1) Move piglit and deps to oe-core. Piglit is for QA purposes only<br>
> >> and pushes the boundaries of "core platform". In a sense this is a<br>
> >> repeat of the discussion we had with Midori... does oe-core contain<br>
> >> everything needed to sufficiently exercise the core components it<br>
> >> ships or not?<br>
> ><br>
> > I expect Richard will push back on this, and I would support him here.<br>
><br>
> Probably best to let Richard speak for himself here. :)<br>
<br>
</div>:)<br>
<br>
I have to admit I'm leaning towards pulling in the 4 recipes we need<br>
since the win is we get to test the GL stacks.<br>
<br>
We do support graphics in the core, we also do particularly badly at<br>
testing it. That is something I think we need to change. piglit lets us<br>
do that and its not like it has a significant number of dependencies.<br>
Having a couple more python modules to test the python stack probably<br>
isn't a bad idea ether. We pruned quite a number of recipes out, this is<br>
a case where we can add a small number for a significant win.</blockquote></div><br>I am in favor of that too. I would like to use piglit too to test GLES on some of our ARM projects. I am not sure when we can get to do it, but i am definitely interested into that, and it's been on a TODO list for some time now.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>