Project

General

Profile

Actions

Bug #2419

closed

Recent AoIP builds failing on osmo-gsm-tester

Added by pespin over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
08/01/2017
Due date:
% Done:

0%

Spec Reference:

Description

Jenkins job building trials for osmo-msc (used in AoIP verison of tests, https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_build-osmo-msc/) looks to be configured to be triggered only by manual means, I guess that's due to being in development on the aoip branch.

This means osmo-gsm-tester is testing AoIP code not up to date, but from more than 1 month ago.

I recently build a complete trial of software using https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-build-all/, which built last revision of aoip branch. Running it with the job https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run-all/ showed there are a lot of issues on that new revision.

To start with, it seems there is some new osmo-bsc config which is now mandatory and we don't have that set up. See https://git.osmocom.org/osmo-gsm-tester/commit/?h=point-code&id=0411af76c902f8556daaef0243e9140a1854d362 . After fixing that however, there seems to be other more deep issues which need to be solved.


Related issues

Blocks OsmoGSMTester - Bug #2415: osmo-bts-sysmo sometimes ending prematurelyRejectedpespin08/01/2017

Actions
Actions #1

Updated by pespin over 6 years ago

There also seems to be some crashes in the old version of osmo-msc we are using in the hourly jenkins job. Those may be fixed in newer versions of osmo-msc as I guess there has been a lot of changes during last month.

[6471413.145376] osmo-msc[26755]: segfault at 100108 ip 00007fa2d937bb65 sp 00007fffa3db27d0 error 6 in libosmocore.so.
8.0.0[7fa2d936f000+1f000]

lynxis did you find the related coredump file somewhere? do you remember where it is?

Actions #2

Updated by pespin over 6 years ago

  • Blocks Bug #2415: osmo-bts-sysmo sometimes ending prematurely added
Actions #3

Updated by neels over 6 years ago

  • Status changed from New to In Progress
Actions #4

Updated by neels over 6 years ago

  • Status changed from In Progress to Resolved

fixed by https://gerrit.osmocom.org/#/c/3413/ https://gerrit.osmocom.org/#/c/3414/

What was missing:

- configuration of point-codes in the .cfg files.
- a re-build of osmo-hlr with the new default GSUP port of 4222.

This brought attention to the need for automatic builds of the most recent aoip code: installed git on jenkins master in order to fix SCM polling (caused a stale osmo-hlr), and will figure out a way to trigger a re-build of osmo-msc and osmo-bsc from most recent code; possibly only when we move to the new split repositories (#2423).

I could not reproduce any segfault in libosmocore.so as posted above.

Actions #5

Updated by laforge over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)