Commit Graph

6 Commits

Author SHA1 Message Date
Alexander Kanavin
750293518d oeqa/weston: correctly run wayland-info when systemd is in use
Under systemd weston's socket is in /run, not in /run/user/0.

(From OE-Core rev: ea7dfd857ce3779745dccda0cbfd93b5e5de1a36)

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-06 22:39:04 +00:00
Alexander Kanavin
21c1658945 wayland-utils: introduce a recipe
wayland-utils contains wayland-info utility which deprecates
and replaces weston-info from weston.

(From OE-Core rev: bb8fa9950e716fdcee818a38dc4df3a19b1f3c2f)

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-11-11 10:08:12 +00:00
Alexander Kanavin
a839c9ba88 weston-init: correctly start under systemd
Several issues are addressed:
1. weston requires pam when starting under systemd
2. systemd was attempting to launch weston twice (from
sysvinit script and from systemd unit file) which caused confusion
and errors.
3. runtime test should stop/start weston via systemd only if systemd
actually controls system startup, not merely when systemd is present.

(From OE-Core rev: 72dd74c5d384dbe641cc7c02ecf766ff8d5f555f)

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-11-11 10:08:12 +00:00
Khem Raj
bdfc4fb0e9 oeqa/weston: Fix tests to run with systemd
Currently, weston tests fail when using systemd, fix it by providing
transient unit file and inject it via systemd-run, which generates a
service file automatically and launches another weston instance to test
if it can launch a nested instance. Use systemctl stop to end the
service and cleanup, instead of brutal kill

(From OE-Core rev: 7572158b861cb5d4ebf6360ced08ab41419d74d3)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-09-14 22:42:30 +01:00
Yeoh Ee Peng
2492d4fa53 oeqa/runtime/weston: Enhance weston tests
Existing weston test available make sure that a process
for weston-desktop-shell exist when image boot up.

Enhance weston tests by:
 - execute weston-info to make sure weston interface(s)
   are initialized
 - execute weston and make sure it can initialize a
   new wayland compositor (retry checking for
   wayland processes up to 5 times)
 - enable weston logging for debugging when fail
   to initialize wayland compositor

[YOCTO# 10690]

(From OE-Core rev: d06552c588bde8fc15c23d8fc2eb00a4243cbc3b)

Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-04-26 14:00:49 +01:00
Alexander Kanavin
ae6ec0b809 weston: add a basic runtime test
The test is checking that weston is able to start.

(From OE-Core rev: 57700767f90eea8f2b78187c42581aca42d50bbf)

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-02-18 23:53:54 +00:00