Re: [PATCH wayland v2 8/8] tests: Test that one can fetch the protocol error after EPIPE

2015-12-29 Thread Jonas Ådahl
On Tue, Dec 29, 2015 at 11:15:38AM +, Daniel Stone wrote: > Hi Jonas, > > On 29 December 2015 at 02:10, Jonas Ådahl wrote: > > + /* The server will not actually destroy the client until it receives > > +* input, so send something to trigger the client destruction. */ > > +

Re: [PATCH wayland v2 8/8] tests: Test that one can fetch the protocol error after EPIPE

2015-12-29 Thread Daniel Stone
Hi Jonas, On 29 December 2015 at 02:10, Jonas Ådahl wrote: > + /* The server will not actually destroy the client until it receives > +* input, so send something to trigger the client destruction. */ > + callback = wl_display_sync(client->wl_display); > + wl_callback_des

[PATCH wayland v2 8/8] tests: Test that one can fetch the protocol error after EPIPE

2015-12-28 Thread Jonas Ådahl
If a client is terminated due to some reason, it should always be possible to retrieve protocol error associated with the termination. Test that, while either using the dispatch helpers (wl_display_dispatch(_queue)() or the prepare read API, it should be possible to retrieve the error after EPIPE.