[Buildbot-status]Buildbot failure in Python on s390x Debian 3.x
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık arilik.ismail@gmail.com
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık arilik.ismail@gmail.com
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
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, stephane@wirtel.be wrote:
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık < arilik.ismail@gmail.com>
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
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/test_concurrent_futures.py", line 122, in setUp self._prime_executor() File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/test/test_concurrent_futures.py", 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/test_concurrent_futures.py", 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/thread.py", line 160, in submit self._adjust_thread_count() File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/concurrent/futures/thread.py", line 181, in _adjust_thread_count t.start() File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/threading.py", 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, pablogsal@gmail.com 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, stephane@wirtel.be wrote:
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık < arilik.ismail@gmail.com>
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Yep but maybe we could use qemu-system-s390x on our laptop/computer and try to fix this issue.
What do you think of? because of course I don't have a S390x at home, but we could try to emulate it.
Stéphane
On 11/04, 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, stephane@wirtel.be wrote:
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık < arilik.ismail@gmail.com>
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
My suspicions is that is something in the buildbot, because the commit that failed to build has no relevant changes.
For testing this, I have triggered a rebuild of a previous commit that was built correctly. If that one fails then is a configuration problem a we should talk to the buildbot owner.
There are other s390x buildbots and they don't have this problem :(
On Sun, 4 Nov 2018, 14:01 Stephane Wirtel, stephane@wirtel.be wrote:
Yep but maybe we could use qemu-system-s390x on our laptop/computer and try to fix this issue.
What do you think of? because of course I don't have a S390x at home, but we could try to emulate it.
Stéphane
On 11/04, 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, stephane@wirtel.be wrote:
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık < arilik.ismail@gmail.com>
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
David,
Any ideas?
Thanks!
On Nov 4, 2018, at 09:28, Pablo Galindo Salgado pablogsal@gmail.com wrote:
My suspicions is that is something in the buildbot, because the commit that failed to build has no relevant changes.
For testing this, I have triggered a rebuild of a previous commit that was built correctly. If that one fails then is a configuration problem a we should talk to the buildbot owner.
There are other s390x buildbots and they don't have this problem :(
On Sun, 4 Nov 2018, 14:01 Stephane Wirtel, stephane@wirtel.be wrote: Yep but maybe we could use qemu-system-s390x on our laptop/computer and try to fix this issue.
What do you think of? because of course I don't have a S390x at home, but we could try to emulate it.
Stéphane
On 11/04, 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, stephane@wirtel.be wrote:
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık < arilik.ismail@gmail.com>
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Ned Deily nad@python.org -- []
Yesterday, all of the s390 buildbot VMs were moved to a new system, but the VMs themselves were unchanged.
It's possible that there is some bad interaction between Debian kernel and the new hardware causing the new test failures.
- David
On Sun, Nov 4, 2018 at 9:31 AM Ned Deily nad@python.org wrote:
David,
Any ideas?
Thanks!
On Nov 4, 2018, at 09:28, Pablo Galindo Salgado pablogsal@gmail.com wrote:
My suspicions is that is something in the buildbot, because the commit that failed to build has no relevant changes.
For testing this, I have triggered a rebuild of a previous commit that was built correctly. If that one fails then is a configuration problem a we should talk to the buildbot owner.
There are other s390x buildbots and they don't have this problem :(
On Sun, 4 Nov 2018, 14:01 Stephane Wirtel, stephane@wirtel.be wrote: Yep but maybe we could use qemu-system-s390x on our laptop/computer and try to fix this issue.
What do you think of? because of course I don't have a S390x at home, but we could try to emulate it.
Stéphane
On 11/04, 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, stephane@wirtel.be wrote:
It's not the first issue on this worker. maybe we should check the worker and fix the issue.
On 11/03, buildbot@python.org wrote:
The Buildbot has detected a failed build on builder s390x Debian 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/13/builds/1869
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: edelsohn-debian-z
Build Reason: <unknown> Blamelist: Stéphane Wirtel stephane@wirtel.be, İsmail Arılık < arilik.ismail@gmail.com>
BUILD FAILED: failed test (failure)
Sincerely, -The Buildbot
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Stéphane Wirtel - https://wirtel.be - @matrixise
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
Buildbot-status mailing list -- buildbot-status@python.org To unsubscribe send an email to buildbot-status-leave@python.org https://mail.python.org/mm3/mailman3/lists/buildbot-status.python.org/
-- Ned Deily nad@python.org -- []
participants (5)
-
buildbot＠python.org -
David Edelsohn -
Ned Deily -
Pablo Galindo Salgado -
Stephane Wirtel