ejakowatz e3684651de Finally figured out why the first assert in IsMessageWaiting5() always ... worked under R5 but only sometimes for OBOS. Answer: the OBOS implementation of BLooper was attempting to lock itself prior to fetching the message from the queue. I moved the lock attempt after the fetch and it worked the same. I realized that if the system was loaded heavily enough, the assert might still fail simply because the looper would not had enough time to get to the fetch (thereby emptying the queue), making the assert pretty useless. Given that it was originally there as a probing test (rather than as an integral part of the unit test), there is no real need for it anyway, so it is no longer used. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@250 a95241bf-73f2-0310-859d-f6bbb57e9c96		2002-07-16 07:51:51 +00:00
..
add-ons	Added definition of B_BAD_DATA.	2002-07-15 17:13:15 +00:00
kits	Finally figured out why the first assert in IsMessageWaiting5() always	2002-07-16 07:51:51 +00:00
servers/input	It is accomplished ...	2002-07-09 12:24:59 +00:00
ExampleTest.cpp	Initial checking of unified unit testing app and example test.	2002-07-11 03:34:41 +00:00
ExampleTest.h	Initial checking of unified unit testing app and example test.	2002-07-11 03:34:41 +00:00
ExampleTestAddon.cpp	Initial checkin	2002-07-15 06:59:19 +00:00
Jamfile	Added add-ons test to the build.	2002-07-13 20:43:24 +00:00
UnitTester.cpp	Added dynamic test suite loading	2002-07-15 06:58:52 +00:00
UnitTester.h	Initial checking of unified unit testing app and example test.	2002-07-11 03:34:41 +00:00