Thanks heaps for looking into this!
Sometimes I only get six failures (the last six tests), but usually it
looks like this:
I'm happy to run any other diagnostics that spring to mind, let me
know.
FFFFFFFF
======================================================================
FAIL: test_1_5 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 50, in test_1_5
self.t_scheduled(1, 5, 0)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 1.0088569916008878 != 1 within 2 places
======================================================================
FAIL: test_1_5_d5 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 53, in test_1_5_d5
self.t_scheduled(1, 5, 0.5)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 1.013288560417595 != 1 within 2 places
======================================================================
FAIL: test_d01_50 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 71, in test_d01_50
self.t_scheduled(.01, 50)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 0.015586338487154183 != 0.01 within 2 places
======================================================================
FAIL: test_d02_50 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 68, in test_d02_50
self.t_scheduled(.02, 50)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 0.031199216660217743 != 0.02 within 2 places
======================================================================
FAIL: test_d05_50 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 62, in test_d05_50
self.t_scheduled(.05, 50)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 0.061227893489256502 != 0.050000000000000003 within 2
places
======================================================================
FAIL: test_d05_50_d03 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 65, in test_d05_50_d03
self.t_scheduled(.05, 50, 0.03)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 0.061668731640474039 != 0.050000000000000003 within 2
places
======================================================================
FAIL: test_d1_50 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 56, in test_d1_50
self.t_scheduled(.1, 50)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 0.10863475665203248 != 0.10000000000000001 within 2
places
======================================================================
FAIL: test_d1_50_d05 (__main__.EVENT_LOOP)
----------------------------------------------------------------------
Traceback (most recent call last):
File "EVENT_LOOP.py", line 59, in test_d1_50_d05
self.t_scheduled(.1, 50, 0.05)
File "EVENT_LOOP.py", line 43, in t_scheduled
timeout = event_loop.idle()
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\app\b
ase.py", line 200, in idle
redraw_all = self.clock.call_scheduled_functions(dt)
File "F:\Documents and Settings\jhartley\Desktop\pyglet-read-only
\pyglet\clock
.py", line 312, in call_scheduled_functions
item.func(ts - item.last_ts, *item.args, **item.kwargs)
File "EVENT_LOOP.py", line 24, in f
self.assertAlmostEqual(t - self.last_t, interval, 2)
AssertionError: 0.1085534614036141 != 0.10000000000000001 within 2
places
----------------------------------------------------------------------
Ran 8 tests in 2.515s
FAILED (failures=8)
On Oct 30, 12:42 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote:
> If you are one of the people who have encountered issues with
> scheduling accuracy in pyglet, please take a couple of minutes to run
> this test case on your computer. Your feedback would be especially
> helpful if you are running Windows, which apparently had some serious
> issues for some people in the past (though not all).
>
> To run the test case, check out the latest revision of pyglet from SVN
> (instructions at code.google.com/p/pyglet/source/checkout) and run
>
> python tests/app/EVENT_LOOP.py
>
> Note that this version of pyglet is not stable and so not suitable for
> development -- don't install it.
>
> The test case will take no longer than 30 seconds to run. If the test
> case fails, please try it again. This sort of timing test case is
> bound to fail from time to time, due to nondeterminism in the
> operating system. You may need to quit background processes such as
> games or messaging software if you get repeated failures.
>
> After trying the test case at least 5 times and getting _no_
> successes, please copy the output of one of the runs and email me. If
> it passes at least once, there's no need to email me.
>
> Cheers
> Alex.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
