Elie Tournier <tournier.e...@gmail.com> writes: > On Mon, Jun 24, 2019 at 11:41:55AM -0700, Eric Anholt wrote: >> Elie Tournier <tournier.e...@gmail.com> writes: >> >> > Hi there, >> > >> > Great topic. For the past few days, I was looking at a CI for Mesa: >> > https://gitlab.freedesktop.org/hopetech/tracie >> > OK, it's in a very very alpha stage. ;) >> >> I did one of those things using apitrace diff-images in piglit: >> >> https://gitlab.freedesktop.org/mesa/piglit/tree/master/tests/apitrace >> >> https://github.com/anholt/trace-db >> >> It was bad. diff-images is too picky and you end up needing to bless >> new images constantly. I have decided to not pursue this line of >> testing any further because it was so unproductive. > For now, my plan is to run the CI only once a week. > So efficiency is not my top priority right now. But it will at some point. > > I'm trying to figure out which tools is the best for this job: > Correctness *and* perf testing. > >> >> What I *am* interested in trying with traces for correctness testing is >> using a single driver to replay trace keyframes multiple times and make >> sure the image is invariant. This could catch a large class of UB in >> real world applications without needing continuous human intervention. > So what's happening if an object is not render in all frame?
That would not be something that the tool I want to build could catch, but also I don't think you'll manage to build a tool to do that that doesn't involve a lot of human intervention.
signature.asc
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
