[10:00] <Saviq> https://github.com/MirServer/graphics-core22/pull/4
[10:11] <alan_g[m]> <Saviq> "https://github.com/MirServer/..." <- ${SNAP} isn't the variable you were looking for
[10:12] <Saviq> Indeed.
[11:00] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2884](https://github.com/MirServer/mir/pull/2884): experiment with Sphinx and breathe/exhale
[11:00] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths merged [pull request #2884](https://github.com/MirServer/mir/pull/2884): experiment with Sphinx and breathe/exhale
[11:47] <Saviq> alan_g, hrmf! Any idea why would XWayland tests not show up at all in `mir-test-tools.performance-test`?
[11:48] <Saviq> Looks like we've a problemw with XWayland in general in base: core22, just it never ran because it's skipped somehow
[11:48] <alan_g[m]> IIRC we skip have to those if the x11 interface is connected (because it mounts weird stuff)
[11:49] <Saviq> Ah.
[11:49] <Saviq> Too much magic.
[11:54] <alan_g[m]> Yes: https://github.com/MirServer/mir-test-tools/blob/main/performance/performance-env.sh
[11:57] <Saviq> Yeah, we should probably get rid of that and make it a responsibility of the user.
[11:57] <Saviq> alan_g can you please see if `mir-test-tools.performance-test --gtest_filter=*XWayland*` works for you on `latest/*`?
[11:57] <Saviq> (it doesn't, here, wonder when it worked, last)…
[12:00] <Saviq> We should also have a smoke test for XWayland…
[12:02] <alan_g[m]> Yeah, I see errors. Will investigate after lunch
[13:08] <alan_g[m]> So. It is a confinement issue. (Installing with devmode means it works.) Will look for a workaround...
[13:18] <Saviq> It's black for me still, but the test does complete. It seems to work on 20.04 hosts, is why we didn't notice it failing in the lab
[13:30] <alan_g[m]> I'm testing on 22.04 - and FWIW (with devmode) see the horse
[13:31] <Saviq> 22.10 here well, but black for me on both latest and 22 tracks
[14:22] <alan_g[m]> OK, I know what is wrong. I remember we had a workaround but can't find it
[14:27] <Saviq> Filed https://github.com/MirServer/mir-test-tools/issues/60 to track, may need to spawn separate bugs
[15:08] <alan_g[m]> OK, I have a workaround PR on core20. But it isn't sufficient for core22...
[15:08] <Saviq> Nah, that's something else altogether, I'll be looking into that
[15:09] <alan_g[m]> So you don't need me?
[15:09] <Saviq> For the core22 one, I'll be digging, thanks
[15:25] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq edited [issue #2885](https://github.com/MirServer/mir/issues/2885): core22: XWayland tests failing to start
[15:25] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2885](https://github.com/MirServer/mir/issues/2885): core22: XWayland tests failing to start... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/8f7daf79f4709d281d7fba6b4f652be194f60d92>)
[15:35] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned Saviq to [issue #2885](https://github.com/MirServer/mir/issues/2885): core22: XWayland tests failing to start
[15:49] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [issue #2886](https://github.com/MirServer/mir/issues/2886): We ought to have a way to configure libinput... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9c683159dc689f80ff8d66c07718b33aba5c90b8>)
[18:02] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq closed [issue #2871](https://github.com/MirServer/mir/issues/2871): XWayland broken on eglstream-kms platform
[19:30] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2883](https://github.com/MirServer/mir/pull/2883): Drop legacy workaround