Skip to content
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

nosetests ipykernel #124

Open
xyniceboy opened this issue Apr 17, 2016 · 1 comment
Open

nosetests ipykernel #124

xyniceboy opened this issue Apr 17, 2016 · 1 comment
Milestone

Comments

@xyniceboy
Copy link

xyniceboy commented Apr 17, 2016

E:\install_work\ipykernel-4.3.1>nosetests ipykernel
.....................E.E...S.....................................................
======================================================================
ERROR: printing from forked mp.Process
----------------------------------------------------------------------
Traceback (most recent call last):
  File "e:\install_work\python2.7\lib\site-packages\nose\case.py", line 197, in runTest
    self.test(*self.arg)
  File "e:\install_work\python2.7\lib\site-packages\numpy\testing\decorators.py", line 215, in knownfailer
    raise KnownFailureException(msg)
KnownFailureException: subprocess prints fail on Windows

======================================================================
ERROR: error in mp.Process doesn't crash
----------------------------------------------------------------------
Traceback (most recent call last):
  File "e:\install_work\python2.7\lib\site-packages\nose\case.py", line 197, in runTest
    self.test(*self.arg)
  File "e:\install_work\python2.7\lib\site-packages\numpy\testing\decorators.py", line 215, in knownfailer
    raise KnownFailureException(msg)
KnownFailureException: subprocess prints fail on Windows

----------------------------------------------------------------------
Ran 81 tests in 26.038s

FAILED (SKIP=1, errors=2)

E:\install_work\ipykernel-4.3.1>
@Carreau
Copy link
Member

Carreau commented Apr 18, 2016

These are expected KnownFailure, the question is why does it not report it as known fail on your system.

@Carreau Carreau added this to the no action milestone Apr 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants