[Piglit] [PATCH] glx-oml-sync-control-timing: Make test behavior more stable

Emil Velikov emil.l.velikov at gmail.com
Mon Jul 30 11:06:43 UTC 2018

HI Illia,

Please don't top-post.

On 30 July 2018 at 10:51, Illia Iorin <illia.iorin at gmail.com> wrote:
> ping
> On Tue, Jul 10, 2018 at 2:25 PM Illia Iorin <illia.iorin at gmail.com> wrote:
>> Hello,
>> Full explanation can be found in
Having a bug report is great, but the commit itself should be self sufficient.

>> https://bugs.freedesktop.org/show_bug.cgi?id=89437#c4
You can add this to the commit summary as
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89437

>> 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
>> <mario.kleiner.de at gmail.com> wrote:
>>> On Mon, Jul 9, 2018 at 9:09 PM, Illia Iorin <illia.iorin at gmail.com>
>>> 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

I'm struggling with your explanation in the bugzilla report. Can you
provide a bit more detail?


More information about the Piglit mailing list