<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [IVB] Piglit/glx_GLX_OML_sync_control_timing_-fullscreen_-divisor_2 fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=89437#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [IVB] Piglit/glx_GLX_OML_sync_control_timing_-fullscreen_-divisor_2 fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=89437">bug 89437</a> from <a class="email" href="mailto:illia.iorin@gmail.com" title="Illia <illia.iorin@gmail.com>"> Illia</a> <pre>I made an investigation and came to the conclusion that the behavior of this test is based on such characteristics of the monitor as resolution and frequency, and on the window manager(different behavior on gnome and unity ).With resolution 1600x900 this test pass 88/100 times and with resolution 1920x1080 this test pass 11/100 times. Analyzing how the GLX_OML_sync_control extension implements in mesa, you can see that there are no calculation based on the influencing characteristics. That means this is not a Mesa bug. This bug doesn't depend on gpu intel gpu architecture, because the test behavior the same on the KBL, IVB and HSW. You can have different behavior, if you change the characteristics of the display, or install another window manager. I think it's necessary to make at least one change in this test. I can’t quite understand where this constant(50) was taken. timing.c:311 if (fabs (expected_msc_wallclock_duration - msc_wallclock_duration_stats.mean)> 50) I think we can increase it to 200, after that test will be working more stable.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>