Skip to content

capfd/windows #141

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

Closed
ghost opened this issue May 8, 2017 · 4 comments
Closed

capfd/windows #141

ghost opened this issue May 8, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented May 8, 2017

Occassionally I see these on appveyor with caplog enabled:

[gw1] win32 -- Python 3.6.1 c:\python36-x64\python.exe
self = <CallInfo when='teardown' exception: [Errno 9] Bad file descriptor>
func = <function call_runtest_hook.<locals>.<lambda> at 0x000000DF799C7AE8>
when = 'teardown'
    def __init__(self, func, when):
        #: context of invocation: one of "setup", "call",
        #: "teardown", "memocollect"
        self.when = when
        self.start = time()
        try:
>           self.result = func()
c:\python36-x64\lib\site-packages\_pytest\runner.py:163: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
c:\python36-x64\lib\site-packages\_pytest\runner.py:151: in <lambda>
    return CallInfo(lambda: ihook(item=item, **kwds), when=when)
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:745: in __call__
    return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:339: in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:334: in <lambda>
    _MultiCall(methods, kwargs, hook.spec_opts).execute()
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:613: in execute
    return _wrapped_call(hook_impl.function(*args), self.execute)
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:254: in _wrapped_call
    return call_outcome.get_result()
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:279: in get_result
    raise ex[1].with_traceback(ex[2])
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:265: in __init__
    self.result = func()
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:613: in execute
    return _wrapped_call(hook_impl.function(*args), self.execute)
c:\python36-x64\lib\site-packages\_pytest\vendored_packages\pluggy.py:245: in _wrapped_call
    next(wrap_controller)   # first yield
c:\python36-x64\lib\site-packages\_pytest\capture.py:138: in pytest_runtest_teardown
    self.resumecapture()
c:\python36-x64\lib\site-packages\_pytest\capture.py:85: in resumecapture
    self._capturing.resume_capturing()
c:\python36-x64\lib\site-packages\_pytest\capture.py:295: in resume_capturing
    self.err.resume()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <FDCapture 2 oldfd=9>
    def resume(self):
        self.syscapture.resume()
>       os.dup2(self.tmpfile_fd, self.targetfd)
E       OSError: [Errno 9] Bad file descriptor
c:\python36-x64\lib\site-packages\_pytest\capture.py:387: OSError
@ghost
Copy link
Author

ghost commented May 8, 2017

apparently this is a confirmed issue. see pytest-dev/pytest#2223.

@RonnyPfannschmidt
Copy link
Member

@xoviat at first glance that issue is unrelated, is there perhaps a typo in the number?

@ghost
Copy link
Author

ghost commented May 8, 2017

@RonnyPfannschmidt That error occurs during the test run. The "cannot send" occurs as an "internal error"

https://ci.appveyor.com/project/matysek/pyinstaller/build/2144/job/os2nf20ptg9x2w2y

@ghost
Copy link
Author

ghost commented May 8, 2017

In fact this error is not related to pytest-timeout as the original reporter suggested. It's related to pytest-catchlog as pytest-timeout was not installed on this attempt:

https://ci.appveyor.com/project/matysek/pyinstaller/build/2145/job/wp170x6gdnx3lsr3

This issue was closed.
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

1 participant