[Piglit] Ideas for Wine Test Suite and Mesa Workflow

[Dylan Baker]

Sent from my Nexus 6.
I'm on mobile, please excuse autocorrect fail.
On Feb 24, 2016 21:38, "Zhenbo Li" <litimetal at gmail.com> wrote:
>
> 2016-02-21 21:38 GMT+08:00 Zhenbo Li <litimetal at gmail.com>:
> >
> > I think I can write a functional python script, and submit it to wine.
> > In mesa, it needs to do
> > little(more simple than piglit/tests/igt.py). I'm writing a proof of
> > concept test(piglit/tests/wine)
> > now, and I'm going to send it to this mail list few days later.
>
> Hello,
>
> It costs me some time to read previous code. I've finished my

> proof-of-concept work[1]. As we mentioned before, we can add an
> interpreter for test results in wine, and call it from piglit via a
> simple script.

That will probably work, the only thing to consider with that approach is
that it is more expensive to start an external process than interpret in
piglit's Python process. If there aren't a lot of tests that may not be a
big deal, but if there are thousands of tests you will start to see
overhead.

Dylan

>
> [1]:
https://github.com/Endle/piglit-gsoc/commit/49ab297e9f0e5284b949f54b401c0da609c82d69
>
https://github.com/Endle/wine-gsoc/commit/e278a23b23db3b398231f8cc17877c4513d6fed9
>
> --
> Have a nice day!
> Zhenbo Li
> _______________________________________________
> Piglit mailing list
> Piglit at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/piglit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/piglit/attachments/20160225/bac3a96e/attachment.html>