[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Tests crashing Automatic Build page + Compiling PyGame on Windows



Hey guys my buddy wants his computer. I found a few unittest extensions, one called subunit, designed for pretty much what we have in mind.

Talk soon.


Lenard Lindstrom wrote:
Hi Nicholas,,,

Nicholas Dudfield wrote:
Lenard,

>> if it goes into the wiki then it could be corrupted by someone else

Sorry, I meant to say a link on the wiki to where it is now would be handy.

I am looking into getting the source bundle added to the Pygame download page.

>> Did you install MSYS-DTK-1.0.1?

Yes, I downloaded the MSYS developers tool kit, msysDTK-1.0.1.exe and installed it.

>> Are the tests for revision 1376? Nothing causes problems like running the wrong tests.

Yeah, the tests were run from the svn co directory. The tests were for the svn HEAD at the time, 1376, which I had just built and installed.I even made sure to destroy old pyc files.

>> The subprocess module works better but requires pywin32 be installed for Windows.

Cheers. I'm sorry if popen4 caused any problems for you.

Though it worked most of the time for me I couldn't figure out how to get the "OK" check to work on the automated build site.


This is really odd, I'm nuking my site-packages/pygame directory, building and installing from HEAD and then running the HEAD tests, but I'm still have crashing issues.

What's the difference between mine and your's and marcus's setup?

Compiling issues come to mind but then I recall I had the same problem after downloading your 1376 msi. I nuked the pygame directory before installing that also.

----------------

I realized that the surflock_test.py error that was taking down run_tests.py (for me anyway) was just that I needed to have numpy installed. Then the suite finished but with these errors.

======================================================================
ERROR: see if the destination surface can be passed in to use.
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\Losty\PyGame\trunk\test\transform_test.py", line 114, in test_scale_d
estination
   s2 = pygame.transform.smoothscale(s, (64,64))
ValueError: Only 24-bit or 32-bit surfaces can be smoothly scaled

======================================================================
FAIL: test_average_surfaces (transform_test.TransformTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\Losty\PyGame\trunk\test\transform_test.py", line 239, in test_average
_surfaces
   self.assertEqual(sr.get_at((0,0)), (10,15,70,255))
AssertionError: (8, 12, 66, 255) != (10, 15, 70, 255)

======================================================================
FAIL: test_threshold_surface (transform_test.TransformTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\Losty\PyGame\trunk\test\transform_test.py", line 145, in test_thresho
ld_surface
self.assertEqual(num_threshold_pixels, s1.get_height() * s1.get_width())
AssertionError: 0 != 1024

----------------------------------------------------------------------
Ran 264 tests in 5.703s

FAILED (failures=2, errors=1)


Then running transform_test.py independently:

D:\Losty\PyGame\trunk\test>transform_test.py
.....
----------------------------------------------------------------------
Ran 5 tests in 0.016s

OK


_What the_?

Any ideas guys? What am I doing wrong?

What is your display's color setting? I have 24 bit True Color. 32 bit True Color is more common. This affects the default surface format. I just managed to freeze the unit tests by setting my display to 16 bit High Color.