Also, the error seems to be some resource limit:

ERROR: test_correct_timeout_exception_msg (test.test_concurrent_futures.ThreadPoolAsCompletedTest)
Traceback (most recent call last):
File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/test/", line 122, in setUp
File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/test/", line 141, in _prime_executor
futures = [self.executor.submit(time.sleep, 0.1)
File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/test/", line 141, in <listcomp>
futures = [self.executor.submit(time.sleep, 0.1)
File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/concurrent/futures/", line 160, in submit
File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/concurrent/futures/", line 181, in _adjust_thread_count
File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/", line 847, in start
_start_new_thread(self._bootstrap, ())
RuntimeError: can't start new thread

On Sun, 4 Nov 2018, 13:56 Pablo Galindo Salgado, <> wrote:
This particular platform is not very easy as we cannot get access to the worker :(

I have triggered a forced build to check if this is transient or not.

On Sun, 4 Nov 2018, 13:09 Stephane Wirtel, <> wrote:
It's not the first issue on this worker. maybe we should check the
worker and fix the issue.

On 11/03, wrote:
>The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython.
>Full details are available at:
>Buildbot URL:
>Worker for this Build: edelsohn-debian-z
>Build Reason: <unknown>
>Blamelist: Stéphane Wirtel <>, İsmail Arılık <>
>BUILD FAILED: failed test (failure)
> -The Buildbot
>Buildbot-status mailing list --
>To unsubscribe send an email to

Stéphane Wirtel - - @matrixise
Buildbot-status mailing list --
To unsubscribe send an email to