VTY tests still causing build failures

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.de
Tue Sep 12 23:41:26 UTC 2017


On Mon, Sep 11, 2017 at 09:09:06PM +0200, Harald Welte wrote:
> In https://gerrit.osmocom.org/3899 which has failed in
> https://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/2451/ and
> https://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/2454/

This particular failure is due to a VTY change in libosmocore.  I have fixed it
in osmo-bsc.git, and this needs to be applied to openbsc.git as well.
Change-Id: I77931d6a09c42c443c6936000592f22a7fd06cab

However, let's decide when we stop developing on openbsc.git. Every patch that
is merged to openbsc.git now needs additional work to be applied to osmo-*.git.

Vice versa, we only need to backport serious fixes to openbsc.git, this is one
of them.

Here is the backport to openbsc.git:
https://gerrit.osmocom.org/3921

> I know Neels and others have spend already significant time in the past trying
> to resolve this - unsuccessfully.

That was the testBSCreload running into "Broken Pipe" errors.

If you see more of those, we may want to disable the testBSCreload:

https://gerrit.osmocom.org/3922

~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/20170913/da349ab6/attachment.bin>


More information about the OpenBSC mailing list