<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [All Bisected]igt/testdisplay causes testdisplay.c:789: Failed assertion: ret" href="https://bugs.freedesktop.org/show_bug.cgi?id=85582#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [All Bisected]igt/testdisplay causes testdisplay.c:789: Failed assertion: ret" href="https://bugs.freedesktop.org/show_bug.cgi?id=85582">bug 85582</a> from <a class="email" href="mailto:yi.sun@intel.com" title="Yi Sun <yi.sun@intel.com>"> Yi Sun</a> <pre>(In reply to Paulo Zanoni from <a href="show_bug.cgi?id=85582#c1">comment #1</a>) > Bug fixed by the following IGT commits: > - tests/testdisplay: Fix test status check fumble > - tests: Reenable testdisplay > > Thanks for the report and the fixes. If you think the bug is still there, > please reopen. > > I'm also starting an offline discussion about how you could have noticed > this bug since testdisplay was not being built. As to disabling testdisplay by default, I'm wondering the reason. Though I noticed Chris said it's related to 64bit relocation address, it still doesn't make sense for me. What we should is fix testdisplay to fit for 64bit relocation address, but not disable its building Testdisplay is a mandatory tool to verify each display interfaces mode setting. I think we should build testdisplay by default, but kick it out of automated test cases scope.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>