[SciPy-dev] new version of weave
eric
eric at scipy.org
Mon Jan 7 09:48:07 EST 2002
One possibility is that you have some corrupt stuff left over from the
previous test runs, since you were playing with this earlier.
Can you remove the ~/.python_compiled directory in your home and everything
under it. Also, as you noted earlier, there could be some files left laying
around in your /tmp directory. Trash these if you see them also.
Then run the test again -- hopefully that helped.
In the mean time, I'll try to track down why corrupt files actually matter
(they shouldn't break things)
eric
----- Original Message -----
From: "Prabhu Ramachandran" <prabhu at aero.iitm.ernet.in>
To: <scipy-dev at scipy.org>
Sent: Monday, January 07, 2002 3:44 AM
Subject: [SciPy-dev] new version of weave
> >>>>> "eric" == eric <eric at scipy.org> writes:
>
> eric> Hey folks, I cleaned up a few issues with weave over the
> eric> weekend, and the new files are available for testing. Among
> eric> the things fixed:
>
> eric> * Files in tar ball now have Unix line endings * Fixed a
> eric> few platform specific issues with the catalog found by
> eric> Prabhu * Added support for Solaris with gcc -- all tests
> eric> pass
>
> No luck still. :( I just updated my cvs copy and tried weave.test. I
> even deleted my older ~/.python21_compiled/ directory. I get the
> following error:
>
> [snip]
> repairing catalog by removing key
> Frepairing catalog by removing key
> F.................warning: specified build_dir '_bad_path_' does not exist
or is or is not writable. Trying default locations
> ....warning: specified build_dir '_bad_path_' does not exist or is or is
not writable. Trying default locations
>
............................................................................
......................
> ======================================================================
> ERROR: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1]
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "weave/tests/test_blitz_tools.py", line 152, in check_5point_avg_2d
> self.generic_2d(expr)
> File "weave/tests/test_blitz_tools.py", line 128, in generic_2d
> standard,compiled = self.generic_test(expr,arg_dict,type,size)
> File "weave/tests/test_blitz_tools.py", line 85, in generic_test
> blitz_tools.blitz(expr,arg_dict,{},verbose=0)
> File "weave/blitz_tools.py", line 100, in blitz
> function_catalog.add_function(expr,func,module_dir)
> File "weave/catalog.py", line 549, in add_function
> self.add_function_persistent(code,function)
> File "weave/catalog.py", line 577, in add_function_persistent
> function_list = [function] + cat.get(code,[])
> File "/usr/local/lib/python2.1/shelve.py", line 66, in get
> return self[key]
> File "/usr/local/lib/python2.1/shelve.py", line 71, in __getitem__
> return Unpickler(f).load()
> UnpicklingError: pickle data was truncated
> ======================================================================
> FAIL: check_add_function_ordered (test_catalog.test_catalog)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "weave/tests/test_catalog.py", line 361, in
check_add_function_ordered
> assert(funcs1 == [string.lower,string.upper])
> AssertionError
> ======================================================================
> FAIL: Test persisting a function in the default catalog
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "weave/tests/test_catalog.py", line 281, in
check_add_function_persistent1
> assert(i in pfuncs)
> AssertionError
> ----------------------------------------------------------------------
> Ran 184 tests in 491.451s
>
> FAILED (failures=2, errors=1)
> <unittest.TextTestRunner instance at 0x8202754>
>
>
> I hope I'm not doing something stupid here.
>
> prabhu
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev at scipy.net
> http://www.scipy.net/mailman/listinfo/scipy-dev
>
More information about the SciPy-Dev
mailing list