Project

General

Profile

Actions

Feature #4564

closed

Run ttcn-3 testsuite with centos packages

Added by osmith over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
05/25/2020
Due date:
% Done:

100%

Spec Reference:

Related issues

Related to Cellular Network Infrastructure - Feature #4550: Integrate RPM spec files into Osmocom repositories and build them on OBSResolvedosmith05/13/2020

Actions
Related to Cellular Network Infrastructure - Bug #4569: TTCN3-centos8: netcat doesn't startRejected05/29/2020

Actions
Actions #1

Updated by osmith over 2 years ago

  • Related to Feature #4550: Integrate RPM spec files into Osmocom repositories and build them on OBS added
Actions #2

Updated by osmith over 2 years ago

Concept:
  • in relevant Dockerfiles, put "RUN if ... else ..." for the distro-specific stuff (installing packages etc.)
  • configs and common code for compilation etc. don't need to be duplicated that way
  • add the DISTRO variable to the jenkins.sh scripts that start the testuites
  • modify the jenkins job builder configs to set the DISTRO variable, to debian-stretch and to centos8.
  • for centos8, new jenkins jobs should appear. For example:
    • ttcn3-bts-test (existing)
    • ttcn3-bts-test-latest (existing)
    • ttcn3-bts-test-centos8 (new)
    • ttcn3-bts-test-latest-centos8 (new)

laforge: sounds good?

Actions #3

Updated by osmith over 2 years ago

ttcn3-bts-test-latest-centos8

there are no -latest centos8 packages yet, so these should probably be disabled for now.

Actions #4

Updated by osmith over 2 years ago

  • Tracker changed from Bug to Feature
Actions #5

Updated by laforge over 2 years ago

osmith wrote:

Concept:
  • in relevant Dockerfiles, put "RUN if ... else ..." for the distro-specific stuff (installing packages etc.)
  • configs and common code for compilation etc. don't need to be duplicated that way
  • add the DISTRO variable to the jenkins.sh scripts that start the testuites
  • modify the jenkins job builder configs to set the DISTRO variable, to debian-stretch and to centos8.

makes all sense

  • for centos8, new jenkins jobs should appear. For example:
    • ttcn3-bts-test (existing)
    • ttcn3-bts-test-latest (existing)
    • ttcn3-bts-test-centos8 (new)
    • ttcn3-bts-test-latest-centos8 (new)

let's put those jobs in a new group/folder, something like TTCN3-centos8

Actions #6

Updated by osmith over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 60
Actions #7

Updated by osmith over 2 years ago

  • % Done changed from 60 to 80

On my laptop, I have it working for ttcn3-mgw-tests, the tests are passing. I should be able to finish this with a few more hours tomorrow.

The important logical changes are done, rest is polishing and rolling it out to all containers (not just osmo-mgw):

Here's a jenkins job for testing, but it needs the osmo-ttcn3-hacks patch to function, so it's currently failing.
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-centos8-mgw-test/

Actions #8

Updated by osmith over 2 years ago

  • Related to Bug #4569: TTCN3-centos8: netcat doesn't start added
Actions #9

Updated by osmith over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

Patches are reviewed and merged, and the ttcn-3 testsuites are running for centos8 every day now.

https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/

These testsuites are running correctly:

  • TTCN3-centos-bsc-test-sccplite
  • TTCN3-centos-bts-test
  • TTCN3-centos-ggsn-test
  • TTCN3-centos-hlr-test
  • TTCN3-centos-msc-test
  • TTCN3-centos-pcu-test
  • TTCN3-centos-pcu-test-sns
  • TTCN3-centos-sgsn-test
  • TTCN3-cenots-stp-test

Failing testsuites:

Another unrelated problem are failures on admin2-deb9build, maybe they can simply be resolved by restarting the lxc container: https://osmocom.org/issues/4567

(On a side note, I've renamed the tests from TTCN3-centos8-* to TTCN3-centos-*, because I had created one job with jenkins job builder, then deleted it in the UI and then jenkins job builder did not recreate it anymore, although it should. Debugging why this is the case etc. did not seem like a good use of time at this point, so I did the rename.)

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)