Feature #4564
closedRun ttcn-3 testsuite with centos packages
Added by osmith almost 4 years ago. Updated almost 4 years ago.
100%
Related issues
Updated by osmith almost 4 years ago
- Related to Feature #4550: Integrate RPM spec files into Osmocom repositories and build them on OBS added
Updated by osmith almost 4 years ago
- 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?
Updated by osmith almost 4 years ago
ttcn3-bts-test-latest-centos8
there are no -latest centos8 packages yet, so these should probably be disabled for now.
Updated by laforge almost 4 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
Updated by osmith almost 4 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 60
Updated by osmith almost 4 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/
Updated by osmith almost 4 years ago
- Related to Bug #4569: TTCN3-centos8: netcat doesn't start added
Updated by osmith almost 4 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:
- TTCN3-centos-remsim-test
- remsim get stuck in general, not centos related: https://osmocom.org/issues/4572
- TTCN3-centos-bsc-test
- TTCN3-centos-sip-test
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.)