this bug should be fixed in: Committed revision 1562. cu
On Thu, Jul 31, 2008 at 2:50 PM, Nicholas Dudfield <[EMAIL PROTECTED]> wrote: > As can be seen on the handy build page > (http://thorbrian.com/pygame/builds.php), we have a failing test at the > moment. > > event_test.py:57 last rev: 1539:akalias > FAIL: EventModuleTest.test_set_blocked > > The test is called test_set_blocked, testing pygame.event.set_blocked() > though the issue may be with event.post() bypassing the set_blocked > mechanism. > > def test_set_blocked(self): > # __doc__ (as of 2008-06-25) for pygame.event.set_blocked: > > # pygame.event.set_blocked(type): return None > # pygame.event.set_blocked(typelist): return None > # pygame.event.set_blocked(None): return None > # control which events are allowed on the queue > > pygame.event.set_blocked(2) > > self.assert_(pygame.event.get_blocked(2)) > > pygame.event.post(pygame.event.Event(2)) > > events = pygame.event.get() > should_be_blocked = [e for e in events if e.type == 2] > > self.assertEquals(should_be_blocked, []) > > There is a setUp function that flushes the event queue before each test and > while there is a race condition(OS events) the chances are small it will be > an issue. It is unlikely to cause failure in the consistent fashion that > repeated runs of my own, and all build page, machines are showing. >