This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161221/039669be/attachment.bin>