https://bugs.freedesktop.org/show_bug.cgi?id=60935
Priority: medium
Bug ID: 60935
Assignee: [email protected]
Summary: weston-launch does not handle weston signal exits
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: [email protected]
Hardware: Other
Status: NEW
Version: unspecified
Component: weston
Product: Wayland
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.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Wayland-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
