-
Notifications
You must be signed in to change notification settings - Fork 57
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
Move from nose to pytest #149
Conversation
memo: chainer/chainer#3952 is the key difference between Chainer 3.2 and 4.0 on 2534888 test failure. |
- Chainer has moved to pytest since 3.0.0 and now MN follows. An example of testing tool mismatch is: Chainer's parameterized test started checking all Exceptions including nose SkipTest(), at #3963 and #3876 which are included in 3.2.0 and 4.0, and all unit tests that skips is recognized as test failure. Additionally, this patch starts supporting Chainer 3.2.0 and 2.1.0, dropping 1.x as well (One more issue to support 4.0 remains). - Also, mixture of chainer.testing.attr.gpu and chainer.testing.parametrize, with passing pytest to `-m 'not gpu' does not work in pytest because nose's attributes are direct attribute to test object or function, in contrast to pytest. Thus this patch dissolves all parametrized tests that is using `{gpu: True}, {gpu: False}` or `{nccl: True}, {nccl: False}` as parameters, which is replaced by simple function call patters with `@pytest.mark.gpu` and `@pytest.mark.nccl`. - Add Python 3.6 as test target in Travis. - Fix test_scatter_large_dataset not working for flat communicator
I think its ready for review. And quote from last commit:
|
CI test failures are all against Chainer 2.1 and this is because it's |
As it turned out we don't need any |
Superseded by #167 . |
Chainer has moved to pytest since 3.0.0 and now MN follows.
An example of testing tool mismatch is: Chainer's parameterized test
started checking all Exceptions including nose SkipTest(), at #3963
and #3876 which are included in 3.2.0 and 4.0, and all unit tests that
skips is recognized as test failure. Additionally, this patch starts
supporting Chainer 3.2.0 and 2.1.0, dropping 1.x as well.