<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - weston-launch does not handle weston signal exits"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=60935">60935</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>wayland-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>weston-launch does not handle weston signal exits
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>blocker
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>ullysses.a.eoff@intel.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>weston
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Wayland
          </td>
        </tr></table>
      <p>
        <div>
        <pre>weston-launch does not exit with the exitcode of the weston process when the
weston process is killed by a signal (i.e. SIGTERM, SIGKILL, SIGABRT, SIGSEGV).
This is bad for detecting if weston crashed during an automated test.  It seems
I always get a "Hangup" message with exitcode 129 regardless of how I kill
weston.  This makes it even more difficult (from a testing perspective) to
detect "weston as the cause" for test failures.

weston-launch should exit with the same exitcode as weston in all scenarios.

Setting severity as blocker since weston-launch can't be reliably used for
automated testing.

A fix for this should be back-ported to the 1.0 tag, too.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>