Mir

  1. Bug #1317370
  2. Comment #2

Comment 2 for bug 1317370

Revision history for this message
Alan Griffiths (alan-griffiths) wrote : Re: New unit test "BufferQueueTest.compositor_never_owns_client_buffers" is very slow (10-20 seconds)

I've seen very variable times for BufferQueueTest.* (as run by ctest) but I've not been able to reproduce this specific problem.

E.g.

$ bin/mir_unit_tests --gtest_filter=BufferQueueTest.compositor_never_owns_client_buffers --gtest_repeat=1000 | grep OK | sort --reverse --key=5.2 -b -n | tee tmp.txt | head
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (126 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (124 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (115 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (110 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (110 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (108 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (108 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (107 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (107 ms)
[ OK ] BufferQueueTest.compositor_never_owns_client_buffers (105 ms)

OTOH I've seen

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >'
what(): unexpected release: buffer was not given to compositor