-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assorted errors #331
Comments
There are also [http://build.cmi.kent.edu:8010/builders/Windows_XP%7Etrunk%7Equick/builds/47/steps/trial/logs/problems some errors] that only affect Windows. (view as text)
==================================================================h4.
FAIL: _test (fipy.meshes.gmshImport.Gmsh2D)
Doctest: fipy.meshes.gmshImport.Gmsh2D._test
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Python27\lib\doctest.py", line 2166, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for fipy.meshes.gmshImport.Gmsh2D._test
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~quick\build\fipy\meshes\gmshImport.py", line 1678, in _test
----------------------------------------------------------------------
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~quick\build\fipy\meshes\gmshImport.py", line 1871, in fipy.meshes.gmshImport.Gmsh2D._test
Failed example:
if sys.platform h2. 'win32':
os.close(ftmp)
Exception raised:
Traceback (most recent call last):
File "C:\Python27\lib\doctest.py", line 1254, in __run
compileflags, 1) in test.globs
File "<doctest fipy.meshes.gmshImport.Gmsh2D._test[43]>", line 2, in <module>
os.close(ftmp)
OSError: [9](Errno) Bad file descriptor
==============================================================h2.
FAIL: _test (fipy.meshes.gmshImport.Gmsh3D)
Doctest: fipy.meshes.gmshImport.Gmsh3D._test
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Python27\lib\doctest.py", line 2166, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for fipy.meshes.gmshImport.Gmsh3D._test
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~quick\build\fipy\meshes\gmshImport.py", line 2005, in _test
----------------------------------------------------------------------
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~quick\build\fipy\meshes\gmshImport.py", line 2166, in fipy.meshes.gmshImport.Gmsh3D._test
Failed example:
if sys.platform 'win32':
os.close(ftmp)
Exception raised:
Traceback (most recent call last):
File "C:\Python27\lib\doctest.py", line 1254, in __run
compileflags, 1) in test.globs
File "<doctest fipy.meshes.gmshImport.Gmsh3D._test[28]>", line 2, in <module>
os.close(ftmp)
OSError: [9](Errno) Bad file descriptor
----------------------------------------------------------------------
Ran 538 tests in 229.502s
FAILED (failures=2) Trac comment by guyer on 08-09-2012 at 14:31 |
The the Trac comment by guyer on 08-09-2012 at 14:32 |
The Windows errors are because the Trac comment by guyer on 08-09-2012 at 14:34 |
The final is because Python 2.x and Py3k write out the POS file at different precisions. Not sure how to resolve that. Trac comment by guyer on 08-09-2012 at 14:36 |
Replying to guyer:
r5278 introduces a somewhat clumsy parsing of the POS file to work around the precision issues. Trac comment by guyer on 08-09-2012 at 16:10 |
There's also [http://build.cmi.kent.edu:8010/builders/Windows_XP%7Etrunk%7Efull/builds/43/steps/trial_1/logs/problems an error], introduced in r5216, that arises for non-PySparse solvers: ====================================================================h2.
FAIL: justErrorVector (fipy.terms.term.Term)
Doctest: fipy.terms.term.Term.justErrorVector
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Python27\lib\doctest.py", line 2166, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for fipy.terms.term.Term.justErrorVector
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~full\build\fipy\terms\term.py", line 308, in justErrorVector
----------------------------------------------------------------------
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~full\build\fipy\terms\term.py", line 328, in fipy.terms.term.Term.justErrorVector
Failed example:
len(DiffusionTerm().justErrorVector(v)) m.numberOfCells
Exception raised:
Traceback (most recent call last):
File "C:\Python27\lib\doctest.py", line 1254, in __run
compileflags, 1) in test.globs
File "<doctest fipy.terms.term.Term.justErrorVector[3]>", line 1, in <module>
len(DiffusionTerm().justErrorVector(v)) == m.numberOfCells
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~full\build\fipy\terms\term.py", line 338, in justErrorVector
solver._solve()
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~full\build\fipy\solvers\scipy\scipySolver.py", line 61, in _solve
self.var[:] = numerix.reshape(self._solve_(self.matrix, self.var.ravel(), numerix.array(self.RHSvector)), self.var.shape)
File "c:\Documents and Settings\wd15\build\Windows_XP~trunk~full\build\fipy\solvers\scipy\linearLUSolver.py", line 64, in _solve_
permc_spec=3)
File "C:\Python27\lib\site-packages\scipy\sparse\linalg\dsolve\linsolve.py", line 173, in splu
ilu=False, options=_options)
RuntimeError: Factor is exactly singular Trac comment by guyer on 08-09-2012 at 16:11 |
Trac comment by guyer on 08-09-2012 at 16:17 |
In c45e062:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In d771651:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In f59b221:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In e6f0d21:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
Marking milestone Trac comment by guyer on 09-30-2013 at 21:44 |
[http://build.cmi.kent.edu:8010/builders/Mac_OS_X_Py3k%7Etrunk%7Equick/builds/42/steps/trial/logs/problems A few errors] have crept in that only affect Py3k
Imported from trac ticket #454, created by guyer on 08-09-2012 at 14:21, last modified: 09-30-2013 at 21:44
The text was updated successfully, but these errors were encountered: