<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [G965] piglit.spec.!opengl 1_2.tex3d-maxsize spins forever" href="https://bugs.freedesktop.org/show_bug.cgi?id=108630#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [G965] piglit.spec.!opengl 1_2.tex3d-maxsize spins forever" href="https://bugs.freedesktop.org/show_bug.cgi?id=108630">bug 108630</a> from <a class="email" href="mailto:andrey.simiklit@gmail.com" title="asimiklit <andrey.simiklit@gmail.com>"> asimiklit</a> <pre>(In reply to Jordan Justen from <a href="show_bug.cgi?id=108630#c8">comment #8</a>) > (In reply to asimiklit from <a href="show_bug.cgi?id=108630#c7">comment #7</a>) > > (In reply to asimiklit from <a href="show_bug.cgi?id=108630#c6">comment #6</a>) > > > I investigated why I missed this regression on my local machine despite I > > > checked this patch several times under piglit and found out that this test > > > passes on my machine even with my original patch. So I guess it depends on > > > some additional things. > > > > > > > The updated patch is delayed due to testing problems. > > I hope my comment ("It is not specific to g965") is not delaying > things. What I meant is that "in theory" it could happen on any system. > But, due to other factors, we only currently know of a reproducible > case on g965. > > So, I would not hold off on re-posting the patch just because you > cannot reproduce the bug on a newer machine. > > -Jordan I just wanted to see "Build # XX - Successful!" from Intel CI for my updated patch to be 100% sure that there are no regressions. But on Friday I was unable to do it due to troubles with a 'mesa-ci.01.org' (I didn't have an ability to see results of Intel CI) and I was unable to get "Success" even for latest mesa master. Today I started one more test run: "global_logic - Build # 37 - Building!" for latest mesa master and when I receive 'Success' I will run it for my updated patch.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>