Bug #2490: osmo-trx build jenkins jobs failing in build2-deb8build (build-2.osmocom.org) - OsmoGSMTester - Open Source Mobile Communications

Actions

Copy link

Bug #2490

closed

osmo-trx build jenkins jobs failing in build2-deb8build (build-2.osmocom.org)

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

Status:

Closed

Priority:

Normal

Assignee:

pespin

Target version:

Start date:

09/04/2017

Due date:

% Done:

100%

Spec Reference:

Description

libuhd seems to be missing in recently added jenkins build slave build2-deb8build (build-2.osmocom.org).

From osmo-gsm-tester manual, that's needed on the debian jessie (and how it's configured in build-1):

# cat /etc/apt/sources.list.d/uhd.list
deb http://ftp.de.debian.org/debian jessie-backports main
# apt-get update
# sudo apt-get install libuhd-dev uhd-host

However, it seems that build-2 is using debian stretch rather than jessie. In that version of debian, we can use the ones from default repo to build osmo-trx, but osmo-trx binaries are not runtime compatible with the libuhd from jessie (some symbols are not found). Which means we need to sort out whether we want to update both build server to the same debian version (stretch) or not, and same goes for osmo-gsm-tester prod/rnd main units. We can discuss this at the office tomorrow.

Once this is sorted out, following wiki page needs to be updated: https://osmocom.org/projects/osmocom-servers/wiki/Jenkins_Node_Setup

Actions

Copy link

Updated by laforge over 6 years ago

what makes you think that build-2 is using stretch? There's a lxc container both for debian8 and for debian9 builds. The latter is not used, the only one configured in jenkins is the debian8 build slave, which has ssh listening on port 10022.

root@build-2 ~ # lxc-ls
deb8build   deb9build   deb9laforge ggsn6

What do we need uhd-host for on the build server? I'm just curious.

I've installed both uhd-host and libuhd-dev from backpors as per your instructions. Please update the wiki page.

Actions

Copy link

Updated by pespin over 6 years ago

Status changed from New to In Progress
Assignee changed from 55360 to pespin

what makes you think that build-2 is using stretch?

I did ssh root@build-2.osmocom.org to see if I could log in (I first thought I had no key installed there), and once logged in, I checked the repositories in /etc/apt/sources.list, and I saw those were from stretch instead of jessie. I thought I was already in the VM used to build stuff but it seems I wasn't.

What do we need uhd-host for on the build server? I'm just curious.

I just followed the manual from osmo-gsm-tester. I uninstalled and tried building osmo-trx and it's working fine, so indeed it's not needed. I'll update the wiki and osmo-gsm-tester manual.