We get this more often than not in the openbsc build job, I'm still not sure how to fix it:
====================================================================== ERROR: testBSCreload (__main__.TestVTYNAT) ---------------------------------------------------------------------- Traceback (most recent call last): File "./vty_test_runner.py", line 785, in testBSCreload b0 = nat_bsc_sock_test(0, "lol") File "./vty_test_runner.py", line 1276, in nat_bsc_sock_test ipa_handle_resp(bsc, tk, verbose) File "./vty_test_runner.py", line 1260, in ipa_handle_resp x.send(IPA().id_resp(IPA().identity(name = tk.encode('utf-8')))) error: [Errno 32] Broken pipe
---------------------------------------------------------------------- Ran 43 tests in 51.717s
FAILED (errors=1)
Reducing the nr of executors hasn't had an effect yet. Could there be another cause? Too fragile timing or something?
~N
Does this happen on any build slave or only with some particular type?
On 18.12.2016 17:30, Neels Hofmeyr wrote:
We get this more often than not in the openbsc build job, I'm still not sure how to fix it:
====================================================================== ERROR: testBSCreload (__main__.TestVTYNAT)
Traceback (most recent call last): File "./vty_test_runner.py", line 785, in testBSCreload b0 = nat_bsc_sock_test(0, "lol") File "./vty_test_runner.py", line 1276, in nat_bsc_sock_test ipa_handle_resp(bsc, tk, verbose) File "./vty_test_runner.py", line 1260, in ipa_handle_resp x.send(IPA().id_resp(IPA().identity(name = tk.encode('utf-8')))) error: [Errno 32] Broken pipe
Ran 43 tests in 51.717s
FAILED (errors=1)
Reducing the nr of executors hasn't had an effect yet. Could there be another cause? Too fragile timing or something?
~N
AFAICT it only happens on the linux_amd64_debian8 https://jenkins.osmocom.org/jenkins/computer/OsmocomBuild1/.
~N
On Mon, Dec 19, 2016 at 09:55:46AM +0100, Max wrote:
Does this happen on any build slave or only with some particular type?
On 18.12.2016 17:30, Neels Hofmeyr wrote:
We get this more often than not in the openbsc build job, I'm still not sure how to fix it:
====================================================================== ERROR: testBSCreload (__main__.TestVTYNAT)
Traceback (most recent call last): File "./vty_test_runner.py", line 785, in testBSCreload b0 = nat_bsc_sock_test(0, "lol") File "./vty_test_runner.py", line 1276, in nat_bsc_sock_test ipa_handle_resp(bsc, tk, verbose) File "./vty_test_runner.py", line 1260, in ipa_handle_resp x.send(IPA().id_resp(IPA().identity(name = tk.encode('utf-8')))) error: [Errno 32] Broken pipe
Ran 43 tests in 51.717s
FAILED (errors=1)
Reducing the nr of executors hasn't had an effect yet. Could there be another cause? Too fragile timing or something?
~N
On Sun, Dec 18, 2016 at 05:30:40PM +0100, Neels Hofmeyr wrote:
We get this more often than not in the openbsc build job, I'm still not sure how to fix it:
====================================================================== ERROR: testBSCreload (__main__.TestVTYNAT)
Traceback (most recent call last): File "./vty_test_runner.py", line 785, in testBSCreload b0 = nat_bsc_sock_test(0, "lol") File "./vty_test_runner.py", line 1276, in nat_bsc_sock_test ipa_handle_resp(bsc, tk, verbose) File "./vty_test_runner.py", line 1260, in ipa_handle_resp x.send(IPA().id_resp(IPA().identity(name = tk.encode('utf-8')))) error: [Errno 32] Broken pipe
Ran 43 tests in 51.717s
FAILED (errors=1)
Reducing the nr of executors hasn't had an effect yet. Could there be another cause? Too fragile timing or something?
I've reduced the nr of executors from 6 down to 2 now. If this 'broken pipe' still appears, I can set it back up. Although things don't necessarily go faster with more executors, we build with 'make -j 9'.
~N
On Wed, Dec 21, 2016 at 02:15:45PM +0100, Neels Hofmeyr wrote:
Although things don't necessarily go faster with more executors, we build with 'make -j 9'.
Correction: I notice that in the python tests phase of the openbsc build, the build slave's CPU is 97% idle... One of those things I'd like to understand one day: why those are so slow and how to speed them up.
~N
-
Max -
Neels Hofmeyr