-
Notifications
You must be signed in to change notification settings - Fork 149
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
CIs error on deprecation warning #708
CIs error on deprecation warning #708
Conversation
The version here [generates deprecations](https://app.circleci.com/jobs/github/usnistgov/fipy/2031) and [ez_setup.py itself is deprecated](pypa/setuptools#581)
* Change "FORTRAN" array ordering to 'F' `order="FORTRAN"` has been deprecated in numpy for awhile and has been [removed in numpy 1.18](https://numpy.org/devdocs/release/1.18.0-notes.html)
The version here [generates deprecations](https://app.circleci.com/jobs/github/usnistgov/fipy/2031) and [ez_setup.py itself is deprecated](pypa/setuptools#581)
…v/fipy into CIs_error_on_DeprecationWarning
This stuff was deprecated [ages ago](https://sourceforge.net/p/pysparse/git/ci/241a05d7a6e5f0f8ae28c53ac79a2111fe2d7cc0/)
The itsolvers classes aren't written right (e.g., `solve()` doesn't return anything) and don't encapsulate anything we care about. The `krylov` calls are set up the way we expect.
Raising errors for all of `python setup.py test` causes errors for deprecations in things we don't control, like versioneer.
Avoid DeprecationWarning
This isn't working for me. If say I add
near the top of |
Also, we're getting |
@wd15 I saw the |
Nevermind. I see, there is no traceback. |
|
@wd15 I get ======================================================================
FAIL: my_func (fipy.variables.variable)
Doctest: fipy.variables.variable.my_func
----------------------------------------------------------------------
Traceback (most recent call last):
File "/Users/guyer/anaconda/envs/fipy/lib/python2.7/doctest.py", line 2226, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for fipy.variables.variable.my_func
File "/Users/guyer/Documents/research/FiPy/fipy/fipy/variables/variable.py", line 21, in my_func
----------------------------------------------------------------------
File "/Users/guyer/Documents/research/FiPy/fipy/fipy/variables/variable.py", line 23, in fipy.variables.variable.my_func
Failed example:
my_func()
Exception raised:
Traceback (most recent call last):
File "/Users/guyer/anaconda/envs/fipy/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
File "<doctest fipy.variables.variable.my_func[0]>", line 1, in <module>
my_func()
File "/Users/guyer/Documents/research/FiPy/fipy/fipy/variables/variable.py", line 31, in my_func
DeprecationWarning
DeprecationWarning: in my_func
----------------------------------------------------------------------
Ran 347 tests in 18.455s
FAILED (failures=1) |
@wd15 Your test case generates an error for me with Python 2.7.15, but not with Python 3.6.7 |
In Py3k, TestProgram makes it very hard to change DeprecationWarnings into errors. [TestProgram gives all warnings an action of `default`](https://github.com/python/cpython/blob/master/Lib/unittest/main.py#L84) which causes [TestRunner to clobber our DeprecationWarning filter](https://github.com/python/cpython/blob/master/Lib/unittest/runner.py#L167) (passing any other action to TestProgram just causes that action to clobber instead)
@wd15 I managed to get DeprecationWarning to throw on Py3k as well |
scikit-fmm (and maybe others) needs VC++ 9.0 https://help.appveyor.com/discussions/problems/26278-organization-build-fails-because-vc-90-is-not-present
[Exclude unwanted build configurations](https://www.appveyor.com/docs/build-configuration/#exclude-configuration-from-the-matrix)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me now
Cause
DeprecationWarning
to raise an Exception when the CIs run the tests.Try to prevent things like #703 from sneaking up on us