Oops.. I hadn't even noticed I was running in 16 bits! I think it's
reasonable to require 24 bits until all works there, and then start
looking at lower color depths.

I run the suite with --no-regression-check and all image tests looked
OK except for image.TEXTURE_GRID. No window came up when I ran the
test on its own, and I get an access violation if I run it after the
regression tests.

Press return to begin test...
INFO:root:Begin unit tests for image.TEXTURE_GRID
Traceback (most recent call last):
  File "\loewis\25\python\Modules\_ctypes\callbacks.c", line 206, in
'calling ca
llback function'
  File "c:\pyglet\pyglet\window\win32\__init__.py", line 611, in
_wnd_proc
    c_int(wParam), c_int(lParam))
WindowsError: exception: access violation reading 0x00000000

I got some more errors I think I must have accidentally edited out
last time (sorry for the n00b question, but any easy way to capture
the output to a file?).

Press return to begin test...
INFO:root:Begin unit tests for image.TEXTURE_GRID
INFO:root:6 tests run
[P]assed test, [F]ailed test: f
Enter failure description:
> Nothing happened.
ERROR:root:User marked fail for image.TEXTURE_GRID
ERROR:root:Nothing happened.
INFO:root:layout.FONTS is marked not implemented, skipping.
INFO:root:layout.HTML is marked not implemented, skipping.
INFO:root:layout.HTML_BUILDER is marked not implemented, skipping.
INFO:root:layout.INLINE_FORMATTING is marked not implemented,
skipping.
INFO:root:layout.INLINE_REPLACED is marked not implemented, skipping.
INFO:root:Testing model.obj.OBJ_LOAD.
ERROR:root:Cannot load test for model.obj.OBJ_LOAD
Traceback (most recent call last):
  File "tests/test.py", line 674, in main
    module = component.get_module(test_root)
  File "tests/test.py", line 257, in get_module
    module = __import__(name)
ImportError: No module named model.obj.OBJ_LOAD
INFO:root:Testing resource.COMPLIANCE.
ERROR:root:Cannot load test for resource.COMPLIANCE
Traceback (most recent call last):
  File "tests/test.py", line 674, in main
    module = component.get_module(test_root)
  File "tests/test.py", line 257, in get_module
    module = __import__(name)
ImportError: No module named resource.COMPLIANCE
INFO:root:Testing resource.REQUIRE.
ERROR:root:Cannot load test for resource.REQUIRE
Traceback (most recent call last):
  File "tests/test.py", line 674, in main
    module = component.get_module(test_root)
  File "tests/test.py", line 257, in get_module
    module = __import__(name)
ImportError: No module named resource.REQUIRE
INFO:root:Testing scene2d.FLAT_OOB.
------------------------------------------------------------------------------
Testing flat map allow_oob enforcement.

Press arrow keys to move view focal point (little ball) around map.
Press "o" to turn allow_oob on and off.

You should see no black border with allow_oob=False.

Press escape or close the window to finish the test.

Press return to begin test...
INFO:root:Begin unit tests for scene2d.FLAT_OOB
ERROR:root:Error in scene2d.FLAT_OOB
ERROR:root:Traceback (most recent call last):
  File "c:\pyglet\tests\scene2d\FLAT_OOB.py", line 24, in test_main
    self.set_map(gen_rect_map([[{}]*10]*10, 32, 32))
  File "c:\pyglet\pyglet\ext\scene2d\debug.py", line 83, in
gen_rect_map
    dark = Image2d.from_image(SolidColorImagePattern((150, 150, 150,
NameError: global name 'SolidColorImagePattern' is not defined

There are more scene2d errors which I'll omit since this is a known
issue. This latter NameError was repeated several times, and it
normally caused the next test to freeze, although it would pass on its
own.

model and resource tests are in bad shape too:

NFO:root:Testing model.obj.OBJ_LOAD.
ERROR:root:Cannot load test for model.obj.OBJ_LOAD
Traceback (most recent call last):
  File "tests/test.py", line 674, in main
    module = component.get_module(test_root)
  File "tests/test.py", line 257, in get_module
    module = __import__(name)
ImportError: No module named model.obj.OBJ_LOAD
INFO:root:Testing resource.COMPLIANCE.
ERROR:root:Cannot load test for resource.COMPLIANCE
Traceback (most recent call last):
  File "tests/test.py", line 674, in main
    module = component.get_module(test_root)
  File "tests/test.py", line 257, in get_module
    module = __import__(name)
ImportError: No module named resource.COMPLIANCE
INFO:root:Testing resource.REQUIRE.
ERROR:root:Cannot load test for resource.REQUIRE
Traceback (most recent call last):
  File "tests/test.py", line 674, in main
    module = component.get_module(test_root)
  File "tests/test.py", line 257, in get_module
    module = __import__(name)
ImportError: No module named resource.REQUIRE

The first window test seems broken:

INFO:root:Testing window.CONTEXT_SHARE.
INFO:root:Begin unit tests for window.CONTEXT_SHARE
ERROR:root:Error in window.CONTEXT_SHARE
ERROR:root:Traceback (most recent call last):
  File "c:\pyglet\tests\window\CONTEXT_SHARE.py", line 45, in
test_context_nosha
re_list
    factory = get_factory()
NameError: global name 'get_factory' is not defined

In the window.EVENT_SHOW_HIDE test, no initial show event is printed
out. Subsequent events are printed OK.
In the window.WINDOW_CAPTION test, the counting caption window is too
small to see the numbers, and I can't resize it. The unicode title
looks right.

I suggest you print again the description of the expected results for
each test right before asking if it passed or failed. Some tests have
a lot of output so this text goes out of the terminal window, and the
user may forget some details about what he's expected to check for.

Although the window resize test looked right, I don't know if the size
printed would correspond to the the client area only, or to the whole
window including title bars and borders. A test for the former may be
to draw two rectangular outlines; a green one that is just contained
within the window, and a red one that is just outside it [i.e., the
green rectangle has corners (x0=0, y0=0), (x=client_width - 1,
y=client_height - 1), and the red one has (x0=-1, y0=-1),
(x=client_width, y=client_height)]. Then tell the tester he should see
a green outline in the border of the window, and no red at all.

In the test that captures the mouse, I closed the window when the
mouse was captured. After that, the mouse cursor would appear hidden
in all tests. This is true even if I Ctrl-C out of test.py and restart
with --start-with. I'm going to try rebooting, so I send this right
away.

Later,

Esteban.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to