Torsten Landschoff

Out of curiosity I bisected this and found out, that this commit caused the regression in CPython 3.7: https://github.com/python/cpython/commit/7ea143ae795a9fd57eaccf490d316bdc13ee9065 This relates to this ticket on bpo: https://bugs.python.org/issue29469 *Edit*: The original...

@tiran Did you hear anything back about this? We are facing the same issue: Instead of getting an MemoryError in kubernetes (and dealing with it), the pod will crash. After...

I can confirm this report. Just ran into this because I changed the traefik log level to debug. After fixing my problem I removed the HelmChartConfig again. My expectation was...

We are constantly running into this fault. It seems like the capture functionality of pytest causes this. Basically the problem disappears when capturing of test output is disabled. However, this...

Unfortunately we are still at an ancient pytest version and I am still unable to reproduce this problem. Most of the time this was triggered in a plugin I wrote...

> Is xdist / parallelism involved in your case? No, apart from some tests starting child processes and using threads, but nothing driven from pytest.

I have no idea how this fails for us at random intervals. I just created a test case that forks hundreds of threads, writes thousands of lines to stdout and...

Thing is that fil.write refers to stdout and returns EAGAIN, which can never happen as far as I know. The problem manifests itself only in our GitLab CI, never on...

I added reporting of the O_NONBLOCK flag on sys.stdout to our tests. It is unset at test setup and also at teardown. I wonder if it is set temporarily by...

I finally found the cause in our test suite: We are using TypeScript for some scripting and npm to build the javascript code (basically ensure that the compiled code is...