- 07 Mar, 2014 1 commit
-
-
Kristian Høgsberg authored
-
- 21 Sep, 2013 2 commits
- 11 Jan, 2013 1 commit
-
-
Jason Ekstrand authored
Added a destroy signal to the wl_display object.
-
- 05 Nov, 2012 1 commit
-
-
Jonas Ådahl authored
Check that after a callback removes a proxy that most likely will have several events queued up with the same target proxy, no more callbacks are invoked. Signed-off-by:
Jonas Ådahl <jadahl@gmail.com>
-
- 30 Jun, 2012 3 commits
-
-
Dylan Noblesmith authored
These would either overflow the struct sockaddr_un, or be truncated and leave a non-null-terminated string.
-
Dylan Noblesmith authored
It was failing with missing include files. While here, destroy the ugly "../src/..." include paths used in the tests that was just hacking around this problem in the Makefile: sed -i s/..\\/src\\/// tests/*.c
-
Dylan Noblesmith authored
-
- 14 May, 2012 1 commit
-
-
Kristian Høgsberg authored
-
- 02 May, 2012 1 commit
-
-
Daniel Stone authored
Make sure we include any generated headers from src/ as well, like wayland-version.h. Signed-off-by:
Daniel Stone <daniel@fooishbar.org>
-
- 26 Apr, 2012 1 commit
-
-
Kristian Høgsberg authored
-
- 22 Apr, 2012 1 commit
-
-
Kristian Høgsberg authored
-
- 20 Apr, 2012 3 commits
-
-
Pekka Paalanen authored
Some system C libraries do not offer SOCK_CLOEXEC flag. Add a new header for OS compatibility wrappers. Wrap socket() calls into wl_os_socket_cloexec() which makes sure the O_CLOEXEC flag gets set on the file descriptor. On systems having SOCK_CLOEXEC this uses the old socket() call, and falls back if it fails due to the flag (kernel not supporting it). wayland-os.h is private and not exported. Add close-on-exec tests for both normal and forced fallback paths. Signed-off-by:
Pekka Paalanen <ppaalanen@gmail.com>
-
Pekka Paalanen authored
Add facility for testing how (many) file descriptors survive an exec. This allows implementing O_CLOEXEC tests. Signed-off-by:
Pekka Paalanen <ppaalanen@gmail.com>
-
Pekka Paalanen authored
Detect file descriptor leaks in tests. Add a sanity test to verify that we catch the leaks. Signed-off-by:
Pekka Paalanen <ppaalanen@gmail.com>
-
- 19 Apr, 2012 2 commits
-
-
Pekka Paalanen authored
Test the testing framework itself, so that it catches the errors we expect it to. Signed-off-by:
Pekka Paalanen <ppaalanen@gmail.com>
-
Pekka Paalanen authored
Makes all test targets have the same common make dependencies. Signed-off-by:
Pekka Paalanen <ppaalanen@gmail.com>
-
- 13 Apr, 2012 1 commit
-
-
Kristian Høgsberg authored
-
- 24 Mar, 2012 1 commit
-
-
U. Artie Eoff authored
Wrap all tests with a memory balance check to detect potential memory leaks. Fixed a few tests that had memory leaks contained in the tests themselves. Signed-off-by:
U. Artie Eoff <ullysses.a.eoff@intel.com>
-
- 20 Mar, 2012 1 commit
-
-
Ander Conselvan de Oliveira authored
-
- 06 Mar, 2012 1 commit
-
-
Kristian Høgsberg authored
-
- 05 Mar, 2012 1 commit
-
-
Gaetan Nadon authored
Detected by running distcheck Signed-off-by:
Gaetan Nadon <memsize@videotron.ca>
-
- 04 Mar, 2012 1 commit
-
-
Gaetan Nadon authored
This prevents distcheck from completing. Moving the -lffi at the end of the command fixes the problem. Signed-off-by:
Gaetan Nadon <memsize@videotron.ca>
-
- 03 Mar, 2012 1 commit
-
-
Kristian Høgsberg authored
-
- 02 Mar, 2012 1 commit
-
-
Kristian Høgsberg authored
We use a simple test-runner helper that runs each test in a separate process and reports the pass/fail rate at the end.
-