There is one thing to mention - as long as bots typically don't have a graphical output, wayland should be run in a headless mode. I'm not sure if it's possible to do, but we have to figure out. Alternatively, we could use a fake wayland server from https://cs.chromium.org/chromium/src/ui/ozone/platform/wayland/fake_server.h?q=ui/ozone/platform/wayland/fake_server.h&dr

The X tests spin up Xvfb to run the tests. In a similar fashion, the Chrome Wayland tests should probably spin up a headless weston instance. e.g. weston --backend'='headless-backend.so <args...> and run that.

Given that the biggest part of gpu related code landed. And it's possible run Ozone/Wayland with a separate gpu process. I think we should start to fix this bug and setup a bot to run unittests and telemetry tests.

Robert, who can you suggest to turn to?

It's on me to figure it out. I need to ask some people.

Hi! what's the status of this?

I started looking into it but as yet there are no bots.

Hi again.  Are there any updates?

not yet.

Hi. We have started looking into the headless-backend for weston, and faced quite a severe issue - whenever headless-backend is used, no wl_seat is announced.

wl_seat is a object, which groups keyboard, pointer, touchscreen devices. Also, it is used to create xdg_popups that are the surfaces for menu windows, tooltips and etc [1]

We need to find a way how to get wl_seat announced. 

[1]https://cs.chromium.org/chromium/src/ui/ozone/platform/wayland/xdg_popup_wrapper_v5.cc?type=cs&g=0&l=34