[Wayland-bugs] [Bug 60926] Weston should exit when run on KMS without weston-launch

[bugzilla-daemon at freedesktop.org]

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

--- Comment #6 from U. Artie Eoff <ullysses.a.eoff at intel.com> ---
(In reply to comment #5)
> > Yes, we have weston permissions as suid root and run it that way.  IIRC, the
> > reason we initially avoided weston-launch was because it always return an
> > exitcode of 0 regardless of how weston exited.  This was bad for detecting
> > if weston crashed during an automated test.  Curiously, I just tried running
> > weston-launch again and now I always get a "Hangup" message with exitcode
> > 129 regardless of how I kill weston (i.e. SIGTERM, SIGKILL, SIGABRT,
> > SIGSEGV).  This makes it even more difficult (from a testing perspective) to
> > detect "weston as the cause" for test failures.  Is there any technical
> > reason why weston-launch couldn't exit with weston's exitcode?
> 
> That's a good point - we should do that.

Yes, if we did that, then I wouldn't be entirely opposed to resolving this bug
as Darxus described.  I've added a bug 60935 for it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20130216/ea4b1dc7/attachment.html>