[Bug 81638] [BYT]igt/gem_concurrent_blit some subcases unable to exit sporadically

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=81638

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Chris Wilson <chris at chris-wilson.co.uk> ---
Try with

commit 4f7d4dcae56e5f993f3f0b331556d4df3b0b33ab
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Jul 21 07:54:29 2014 +0100

    Use SIGTERM in replace of SIGQUIT

    SIGTERM is the normal signal to use when instructing a process to exit.
    The only difference is that an unhandled SIGQUIT is meant to generate a
    coredump, which is not what we want, but in practice I encountered an
    issue where SIGTERM seemed to be deliverable more reliably than SIGQUIT
    (in tests using multiple signal helpers).

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140722/0c945930/attachment.html>