diff options
| author | Bryce Harrington <bryce@osg.samsung.com> | 2015-10-20 08:35:43 -0700 |
|---|---|---|
| committer | Bryce Harrington <bryce@osg.samsung.com> | 2015-10-20 08:35:43 -0700 |
| commit | 33598ffe8d692f21eb49cb41afa60226e132a21c (patch) | |
| tree | 78fdab31ee9514fcc6e20a1397242dd5cf650e54 /tests | |
| parent | 3a1580fb47f1f2667d7a39e2b8ca262b25fa77ee (diff) | |
| download | weston-33598ffe8d692f21eb49cb41afa60226e132a21c.tar.gz | |
devices-test: Fix typo 'destroyes' in a comment
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/devices-test.c | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/tests/devices-test.c b/tests/devices-test.c index 8f9feecc..450713e7 100644 --- a/tests/devices-test.c +++ b/tests/devices-test.c @@ -249,17 +249,18 @@ TEST(get_device_after_destroy) struct wl_touch *wl_touch; /* There's a race: - * 1) compositor destroyes device - * 2) client asks for the device, because it has not got - * new capabilities yet - * 3) compositor gets request with new_id for destroyed device + * 1) compositor destroys device + * 2) client asks for the device, because it has not received + * the new capabilities yet + * 3) compositor gets the request with a new_id for the + * destroyed device * 4) client uses the new_id * 5) client gets new capabilities, destroying the objects * - * If compositor just bail out in step 3) and does not create - * resource, then client gets error in step 4) - even though - * it followed the protocol (it just didn't know about new - * capabilities). + * If the compositor just bails out in step 3) and does not + * create the resource, then the client gets an error in step 4) + * - even though it followed the protocol (it just didn't know + * about new capabilities). * * This test simulates this situation */ |