<div dir="ltr">Hello Emil,<div> <div class="gmail_quote"><div dir="ltr">On Mon, Jul 30, 2018 at 2:06 PM Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">HI Illia, Please don't top-post. On 30 July 2018 at 10:51, Illia Iorin <<a href="mailto:illia.iorin@gmail.com" target="_blank">illia.iorin@gmail.com</a>> wrote: > ping > > On Tue, Jul 10, 2018 at 2:25 PM Illia Iorin <<a href="mailto:illia.iorin@gmail.com" target="_blank">illia.iorin@gmail.com</a>> wrote: >> >> Hello, >> Full explanation can be found in Having a bug report is great, but the commit itself should be self sufficient. >> <a href="https://bugs.freedesktop.org/show_bug.cgi?id=89437#c4" rel="noreferrer" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=89437#c4</a> You can add this to the commit summary as Bugzilla: <a href="https://bugs.freedesktop.org/show_bug.cgi?id=89437" rel="noreferrer" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=89437</a> >> If this does not completely clarify the issue. Please specify the >> question. >> >> Sincerely yours, Illia. >> >> On Tue, Jul 10, 2018 at 12:38 AM Mario Kleiner >> <<a href="mailto:mario.kleiner.de@gmail.com" target="_blank">mario.kleiner.de@gmail.com</a>> wrote: >>> >>> On Mon, Jul 9, 2018 at 9:09 PM, Illia Iorin <<a href="mailto:illia.iorin@gmail.com" target="_blank">illia.iorin@gmail.com</a>> >>> wrote: >>> > The fourfold increase in the test failure condition >>> > is due to its unstable work. The old condition was left, >>> > but the test result was changed from fail to warn, added >>> > fail condition. >>> > >>> >>> Hi, can you clarify what the commit message wrt. "fourfold increase... >>> due to its unstable work" means? I'd like to understand the observed >>> issue better. >>> As you can see from git log Michel has improved the first iteration ( The only problem reported as of comment 3 is an occasional failure on the first iteration. Something I believe is fixed with Michel's patch 375a0b8ac845e13c180dafc73cb4b8bc32fffb20 </blockquote><div>This test works unstable at some resolutions. For example, you can run test on all resolutions supported by your display <span style="color:rgb(0,0,0);font-family:Tahoma,sans-serif,Arial,Helvetica;white-space:pre-wrap;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">and see unexpected fails. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> I'm struggling with your explanation in the bugzilla report. Can you provide a bit more detail? </blockquote><div> As I’ve understood from source of Mesa all OML sync calls are redirected to specific implementation of windows manager. It is not mentioned what deviation is permissible in OML Spec. While I was running test on different configurations of gpu arch, resolution and windows manager I came to the conclusion 200 ns is the acceptable delay that helps us to distinguish the error in mesa from the error in the window manager. If we do not change the error condition this part of test do not have sense, because it fails so often and unpredictable, and this “fail” doesn’t show incorrect work of opengl implementation. This workaround helps to catch an error which cause in the implementation of openGL and not in the implementation of the window manager. <div class="gmail_default" style="font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)">Thanks,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)">Illia.</div> </div></div></div></div>