<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 11 Feb 2020 at 18:46, Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 11 Feb 2020 at 16:58, Mark Hatle <<a href="mailto:mark.hatle@kernel.crashing.org" target="_blank">mark.hatle@kernel.crashing.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
I also don't think oe-core itself needs a 'real' UI, and as my previous response<br>
said -- we do need something though to test that the graphical framework is<br>
working properly.<br>
<br>
In the past this often comes back to needing a LOT of a UI in order to<br>
adequately test all of the components of the system. If wayland/weston has a<br>
proper test suite that exercises all of the various parts of and pieces of the<br>
systems -- then the need for a UI drops considerably.<br>
<br>
(but we still have the need for some sort of example/demostration...)<br></blockquote><div><br></div><div>Wayland/weston do have test suites, neither of which we currently use. I don't know how much they exercise all the moving parts, but the tests do exist.</div></div></div></blockquote><div><br></div><div>I have now ran these tests on my host system to see what they do. Both wayland and weston tests are fast (a few seconds each), and here's the outputs for both. I think once these are packaged as ptests and ran on the AB, all that's left is a reasonable demo UI (which as I said could be simply epiphany with working HW acceleration).</div><div><br></div><div>libwayland:<br></div><div> 1/23 wayland-egl symbols check OK 0.08 s <br> 2/23 cpp-compile-test OK 0.02 s <br> 3/23 scanner-test OK 0.18 s <br> 4/23 array-test OK 0.02 s <br> 5/23 client-test OK 0.01 s <br> 6/23 display-test OK 0.57 s <br> 7/23 connection-test OK 0.17 s <br> 8/23 event-loop-test OK 0.17 s <br> 9/23 fixed-test OK 0.01 s <br>10/23 interface-test OK 0.01 s <br>11/23 list-test OK 0.01 s <br>12/23 map-test OK 0.01 s <br>13/23 sanity-test OK 4.44 s <br>14/23 socket-test OK 0.02 s <br>15/23 queue-test OK 0.02 s <br>16/23 signal-test OK 0.01 s <br>17/23 newsignal-test OK 0.01 s <br>18/23 resources-test OK 0.01 s <br>19/23 message-test OK 0.01 s <br>20/23 compositor-introspection-test OK 0.01 s <br>21/23 protocol-logger-test OK 0.01 s <br>22/23 headers-test OK 0.00 s <br>23/23 os-wrappers-test OK 0.02 s <br></div><div><br></div><div>weston:</div><div> 1/26 config-parser OK 0.05 s <br> 2/26 string OK 0.02 s <br> 3/26 vertex-clip OK 0.03 s <br> 4/26 timespec OK 0.05 s <br> 5/26 zuc OK 0.22 s <br> 6/26 bad-buffer OK 0.12 s <br> 7/26 devices OK 2.53 s <br> 8/26 event OK 0.42 s <br> 9/26 keyboard OK 0.23 s <br>10/26 linux-explicit-synchronization OK 0.63 s <br>11/26 internal-screenshot OK 0.19 s <br>12/26 presentation OK 0.19 s <br>13/26 pointer OK 0.53 s <br>14/26 roles OK 0.18 s <br>15/26 subsurface OK 2.08 s <br>16/26 subsurface-shot OK 0.28 s <br>17/26 text OK 0.13 s <br>18/26 touch OK 0.18 s <br>19/26 viewporter OK 2.03 s <br>20/26 xwayland OK 0.48 s <br>21/26 ivi-shell-app FAIL 0.68 s (killed by signal 6 SIGABRT) (needs some image resources in /usr which I didn't install)<br>22/26 plugin-registry OK 0.04 s <br>23/26 surface OK 0.04 s <br>24/26 surface-global OK 0.07 s <br>25/26 ivi-layout-internal OK 0.14 s <br>26/26 ivi-layout OK 0.18 s <br></div><div><br></div><div><br></div><div>Alex<br></div></div></div>