<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [SKL bisected] texsubimage pbo intermittent failures" href="https://bugs.freedesktop.org/show_bug.cgi?id=91926#c63">Comment # 63</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [SKL bisected] texsubimage pbo intermittent failures" href="https://bugs.freedesktop.org/show_bug.cgi?id=91926">bug 91926</a> from <a class="email" href="mailto:topi.pohjolainen@intel.com" title="Topi Pohjolainen <topi.pohjolainen@intel.com>"> Topi Pohjolainen</a> <pre>(In reply to Topi Pohjolainen from <a href="show_bug.cgi?id=91926#c62">comment #62</a>) > I got curious if the failing case is for some reason getting pixel values > for the previous framebuffer. Note that even the simplest case requires two > internal rounds (the test wants to try with different sub-regions - in my > case these are now identical as the region is hardcoded). > I modified the test to use different pixel values for the first and for the > second round. The second round fails and the failing pixel values are such > that would be valid only in the second round (in position 0,8 the values are > such that would be correct for position 0,0). The pixel values are such that > wouldn't be valid for any position in the first round. Interesting enough, this setup also decreases the probability of hitting the bug a lot.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>