Skip to content

Changes

Started by upstream project registry-rebuild-upload-titan #1907
Started 1 yr 11 mo ago
Queued 7.8 sec
Took 59 sec on build2-deb11build-ansible
ttcn3-bts-test: abort if missing osmo-config-merge

Change-Id: I9cea4affac0b3981c88078581a070f98649da667
Oliver Smith at
ttcn3-bts-test: use start_config functions

As suggested by Pau in code review, refactor the file to use functions
for starting the testsuites, SUT and related containers with specific
configurations.

Related: https://gerrit.osmocom.org/c/docker-playground/+/36389/comment/67a7c35e_766943a3/
Change-Id: If3cb7dbe585c03d21e5ec6353fd25575ccac7af0
Oliver Smith at
ttcn3-ggsn-test: ignore failure to kill osmo-ggsn

Don't fail if osmo-ggsn can't be killed at the end of a testsuite
run. This happens currently with ttcn3-ggsn-test-kernel-latest-* jobs,
in the v6_only configurations, because osmo-ggsn latest doesn't support
ipv6 yet and exits. The jenkins.sh should keep going and try other
combinations, and exit without error in the end.

Fixes: d8c51cce ("ttcn3-ggsn-test: run with multiple configurations")
Change-Id: I6f3154a9ef114f31bcb5868ee09d1ebc10f35d07
Oliver Smith at