On Sun, Jan 25, 2015 at 11:12 AM, Tristam MacDonald <[email protected]>
wrote:

> The automatic tests (top app graphics clock resource) pass on Mac, but
> exceptions are logged to the console in the app.EVENT_LOOP test:
>
> 2015-01-25 09:04:06.885 Python[28474:3703441] _createMenuRef called with
> existing principal MenuRef already associated with menu
> 2015-01-25 09:04:06.887 Python[28474:3703441] (
>     0   CoreFoundation                      0x00007fff915d866c
> __exceptionPreprocess + 172
>     1   libobjc.A.dylib                     0x00007fff962ed76e
> objc_exception_throw + 43
>     2   CoreFoundation                      0x00007fff915d851d
> +[NSException raise:format:] + 205
>     3   AppKit                              0x00007fff97ed0895
> -[NSCarbonMenuImpl _createMenuRef] + 62
>     4   AppKit                              0x00007fff97ed01e6
> -[NSCarbonMenuImpl _instantiateCarbonMenu] + 139
>     5   AppKit                              0x00007fff97ecea42
> -[NSApplication finishLaunching] + 947
>     6   libffi.dylib                        0x00007fff91826f44
> ffi_call_unix64 + 76
>     7   ???                                 0x00007fff5952bb80 0x0 +
> 140734691982208
> )
>
> I tried to run the manual interactive tests, but the harness seems to be
> broken on Mac, and won't accept further user input after the initial 'press
> enter'.
>
> - Tristam
>
>
>
This may be a test runner problem:

    issue 728 ( https://code.google.com/p/pyglet/issues/detail?id=728 )
states that Multiple run()/exit() calls on OSX leads to error (and likely
later segfault)

   adding prints in pyglet.app.__init__.py for run and exit print this in
windows xp (i dont have macs to test)

"""
------------------------------------------------------------------------------
Running Test: top.IMPORT (1/141)

Test that all public modules are accessible after importing just 'pyglet'.

This _must_ be the first test run.

------------------------------------------------------------------------------
Running Test: app.EVENT_LOOP (2/141)

Test that the event loop can do timing.

The test will display a series of intervals, iterations and sleep times.
It should then display an incrementing number up to 2x the number of
iterations, at a rate determined by the interval.

Test interval=1, iterations=5, sleep=0
***app.run
***app.exit

Test interval=1, iterations=5, sleep=0.5
***app.run
***app.exit

Test interval=0.01, iterations=50, sleep=0
***app.run
***app.exit

Test interval=0.02, iterations=50, sleep=0
***app.run
***app.exit

Test interval=0.05, iterations=50, sleep=0
***app.run
***app.exit

Test interval=0.05, iterations=50, sleep=0.03
***app.run
***app.exit

Test interval=0.1, iterations=50, sleep=0
***app.run
***app.exit

Test interval=0.1, iterations=50, sleep=0.05
***app.run
***app.exit
"""

Can Larson chime in with some suggestion ?

The scripts under samples/ show any problem ?

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to