Commits on Source (11)
-
Pekka Paalanen authored
This fixes all ASan reported leaks in this test. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
fc26bdb2 -
Pekka Paalanen authored
Fix all ASan reported leaks in this test. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
ecbf1dba -
Pekka Paalanen authored
Not printing these will drop 7980 lines or roughly 350 kB from the test logs. Now I don't have scroll through them all, and I don't have to watch them if I run this test manually. These prints were useful when developing the test, but we don't need them printed in CI all the time. Printing the final count should be enough. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
c021e2f9 -
Pekka Paalanen authored
Fix all ASan reported leaks in this test when running on AMD Mesa driver. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
9cf9121b -
Pekka Paalanen authored
Fix all ASan reported leaks in this test. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
4f515a1d -
Pekka Paalanen authored
Fixes all ASan reported leaks. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
b9826762 -
Pekka Paalanen authored
Fix all ASan reported leaks. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
54ea691b -
Pekka Paalanen authored
Fix all ASan reported leaks. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
56a8d69b -
Pekka Paalanen authored
Fixes all ASan reported leaks. The manual touch release is slightly awkward as we need to open-code a part of input_destroy() to avoid double-freeing pointer->wl_touch. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
a01299a5 -
Pekka Paalanen authored
Fixes all ASan reported leaks in this test when using AMD Mesa driver. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
f6acdc5d -
Pekka Paalanen authored
This fixes all ASan reported leaks in this test. This test program has several tests named *_multiple that just run another test function 30 times. Previously without cleanup all the created clients would be left lingering, but now they are torn down. Ths might cause a change in test behaviour, although that was never the intention: > It is intentional to run it so many times, but it is not intentional > to run a hundred clients at a time. The problem is that currently we > have no destroy function for client. However, the clients do not run > simultaneously but serially, so the effect should be the same as if > we'd destroy them (after the client finishes its body, it just 'is' > and does nothing until the process exits) - the original review discussion in https://lists.freedesktop.org/archives/wayland-devel/2015-March/020957.html The intention for the repeat testing is that as the Weston instance remains from test to another, each test needs to undo its changes to the devices. Failing to correcntly undo would accumulate devices. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
591fa3b9