Project

General

Profile

Bug #3985

osmo-bsc latest package builds fail as of 2019-05-08

Added by laforge 12 days ago. Updated 4 days ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
05/08/2019
Due date:
% Done:

0%

Spec Reference:

Description

Every dist/arch of our latest osmo-bsc packages fail since yesterday (libosmocore tagging):

See e.g. https://build.opensuse.org/package/live_build_log/network:osmocom:latest/osmo-bsc/Debian_8.0/x86_64

[  295s] [0;m[1;32m[1;34mDCHAN[0;m[1;32m lchan_fsm.c:377 lchan(1-0-1-TCH_F-0){UNUSED}: (type=TCH_F) Clearing lchan state
[  295s] [0;m[1;31m[1;34mDTS[  274.540150] serial8250: too much work for irq4
[  295s] [0;m[1;31m lchan_fsm.c:410 timeslot(1-0-1-TCH_F){UNUSED}: Received Event TS_EV_LCHAN_UNUSED
[  295s] [0;m- Expecting channel request at BTS 1 TS 1
[  295s] --- expout    2019-05-08 02:42:21.852000000 +0000
[  295s] +++ /usr/src/packages/BUILD/tests/testsuite.dir/at-groups/36/stdout    2019-05-08 02:42:21.864000000 +0000
[  295s] @@ -1 +1 @@
[  295s] -Test OK
[  295s] +Test failed, because no channel was requested
[  295s] ./testsuite.at:219: exit code was 1, expected 0
[  295s] 36. testsuite.at:216: 36. handover test 28 (testsuite.at:216): FAILED (testsuite.at:219)

Related issues

Related to OsmoSGSN - Bug #3984: osmo-sgsn latest package feed broken as of 2019-05-08Resolved2019-05-08

History

#1 Updated by laforge 12 days ago

  • Project changed from OsmoSGSN to OsmoBSC

#2 Updated by laforge 12 days ago

  • Related to Bug #3984: osmo-sgsn latest package feed broken as of 2019-05-08 added

#3 Updated by pespin 11 days ago

  • Status changed from New to Feedback

After libosmocore new release, some osmo-bsc tests required updating to work again. That's already in osmo-bsc master but not in osmo-bsc last release:
https://git.osmocom.org/osmo-bsc/commit/?id=eda6bfab6b86891e074905af8b7e5dbe0ac18762

So I just created a new patch release 1.4.1 on top of 1.4.0 with that patch:
https://gerrit.osmocom.org/#/c/osmo-bsc/+/13909 handover_fsm: copy old S15_S0 to new lchan
https://gerrit.osmocom.org/#/c/osmo-bsc/+/13910 Bump version: 1.4.0.1-1f6930 → 1.4.1

Furthermore, osmo-mgw master required a fix (otherwise gerrit building that old osmo-bsc release + osmo-mgw master failed). At some point mgw-endpoint FSM was moved from osmo-bsc to osmo-mgw, and API names were changed, but not the FSM name. Following commit in osmo-mgw.git allows old osmo-bsc to build/run with new osmo-mgw: https://gerrit.osmocom.org/#/c/osmo-mgw/+/13912/

commit 182ca3bad43092147fc92e0226533acc9ca81260 (HEAD -> master)
Author: Pau Espin Pedrol <pespin@sysmocom.de>
Date:   Wed May 8 14:01:20 2019 +0200

    mgcp-cli: Change osmo_mgcpc_ep_fsm name to avoid collision with old osmo-bsc

    Recent commit moved mgw_endpoint_fsm from osmo-bsc.git here as
    osmo_mgcpc_ep_fsm. Some API name changes were applied to avoid
    collisions, but FSM was kept and it is registered during startup with
    __attribute__((constructor)). As a result, with old osmo-bsc (+tests)
    try to allocate its copy of mgw_endpoint_fsm, it fails because that name
    is already registered.

    Fixes: 538d2c53d90074267e7a70a90c773baa03d6ec04
    Change-Id: I694ce58baa43f536b7e594b003edc891f029aa4a

#4 Updated by laforge 4 days ago

can this be marked as resolved?

#5 Updated by pespin 4 days ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)