On Thu, 2017-02-23 at 21:59 +0100, Roland Scheidegger wrote: > So, what does the failing test do?
Not much, curiously. There are five that fail and they're all fairly trivial, although the xts harness makes that hard to see. XClearArea/6 and XClearWindow/4 set the window background pixmap to None and calls XClearArea. This should not change any pixels; apparently it does. XClearArea/7 and XClearWindow/5 create a parent window, then a child, sets the parent bg to None, the child to ParentRelative, and clears the child. Again, this should not change anything, but does. XCopyArea/1 creates two windows, tiles the background of the first one (equivalent to ClearWindow), copies from one window to the other, and verifies that the second one has the right content. The first four there are a little strange because, in principle, the thing they're testing is that no rendering happens. Presumably what's being measured is that some _other_ rendering prior to the action under test is being done incorrectly. The CopyArea test is probably closest to the root cause. I'll drill down a bit on exactly what that turns into in terms of GL draws. - ajax _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
