On 09/26/2017 08:47 AM, Brian Paul wrote:
On 09/26/2017 10:32 AM, Thomas Hellstrom wrote:
Tests that check frontbuffer contents after drawing may fail because
the X server touch the front contents between drawing and checking.
In those
cases, there's typically a pending expose event. So check
On 09/26/2017 10:32 AM, Thomas Hellstrom wrote:
Tests that check frontbuffer contents after drawing may fail because
the X server touch the front contents between drawing and checking. In those
cases, there's typically a pending expose event. So check for that
situation and optionally rerun the t
On 09/26/2017 10:55 AM, Thomas Hellstrom wrote:
On 09/26/2017 08:47 AM, Brian Paul wrote:
On 09/26/2017 10:32 AM, Thomas Hellstrom wrote:
Tests that check frontbuffer contents after drawing may fail because
the X server touch the front contents between drawing and checking.
In those
cases, ther
Thomas Hellstrom writes:
> Tests that check frontbuffer contents after drawing may fail because
> the X server touch the front contents between drawing and checking. In those
> cases, there's typically a pending expose event. So check for that
> situation and optionally rerun the test.
Did this
Tests that check frontbuffer contents after drawing may fail because
the X server touch the front contents between drawing and checking. In those
cases, there's typically a pending expose event. So check for that
situation and optionally rerun the test.
Signed-off-by: Thomas Hellstrom
---
tests/
Because in Python we have `bool([]}) == False`, providing empty test
list resulted in hitting the same code path as not providing it at all,
meaning that we run everything.
Let's just exit early with an appropriate message instead.
This will get rid of the rather surprising behavior and will help
