Copyright © 2012 Intel Corporation Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Internal testing facilities for the weston compositor. It can't be stressed enough that these should never ever be used outside of running weston's tests. The weston-test.so module should never be installed. These requests may allow clients to do very bad things. Request that the compositor pauses execution at a certain point. When execution is paused, the compositor will signal the shared semaphore to the client. This is a global singleton interface for Weston internal tests. This interface allows a test client to trigger compositor-side test procedures. This is useful for cases, where the actual tests are in compositor plugins, but they also require the presence of a particular client. This interface is implemented by the compositor plugins containing the testing code. A test client starts a test with the "run" request. It must not send another "run" request until receiving the "finished" event. If the compositor-side test succeeds, the "finished" event is sent. If the compositor-side test fails, the compositor should send the protocol error "test_failed", but it may also exit with an error (e.g. SEGV). Unknown test name will raise "unknown_test" protocol error.