Started by an SCM change3097ac0902cd740139b0d1cfdbd90179de7379d28837ac0902cd740139b0d1cfdbd90179de7379d2883refs/remotes/origin/osmith/wip-dahdi7ac0902cd740139b0d1cfdbd90179de7379d28837ac0902cd740139b0d1cfdbd90179de7379d2883refs/remotes/origin/osmith/wip-dahdi336713468b295cf55e77058b01ea6100047b3739a0f713468b295cf55e77058b01ea6100047b3739a0frefs/remotes/origin/master713468b295cf55e77058b01ea6100047b3739a0f713468b295cf55e77058b01ea6100047b3739a0frefs/remotes/origin/master713468b295cf55e77058b01ea6100047b3739a0f713468b295cf55e77058b01ea6100047b3739a0frefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#3362153255update-osmo-ci-on-slaves-dp #336336falsefalse336716279SUCCESS1649357466252https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/336/gtp0-deb9build- ttcn3-ggsn-test/jenkins-ogs.shttcn3-ggsn-test/ogs/upfd.yamlttcn3-ggsn-test/ogs/smfd.yamlttcn3-ggsn-test/ogs/open5gs-smf.yamlttcn3-ggsn-test/ogs/open5gs-upf.yamlcc7f9b48969d139a4524ed46a8099d9386b3248f1649353016000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-ggsn-ogs: Rename config files
Let's make names similar to what's used in PGW_Tests. Also, in
open5gs.git, config files don't contain the "d" at the end.
Change-Id: If56d1a890a4f1b80b4f04ae22644f9cb9cdd35f4
2022-04-07 19:36:56 +0200cc7f9b48969d139a4524ed46a8099d9386b3248fttcn3-ggsn-ogs: Rename config fileseditttcn3-ggsn-test/jenkins-ogs.shdeletettcn3-ggsn-test/ogs/smfd.yamldeletettcn3-ggsn-test/ogs/upfd.yamladdttcn3-ggsn-test/ogs/open5gs-smf.yamladdttcn3-ggsn-test/ogs/open5gs-upf.yaml
- ttcn3-pgw-test/jenkins.sh8063cd7da1706973862be833bb1e01aaed4277a41649353233000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-pgw-test: Log stdout to find crashes
Change-Id: I573637866787ce1f613bd56a009251578c98cbf3
2022-04-07 19:40:33 +02008063cd7da1706973862be833bb1e01aaed4277a4ttcn3-pgw-test: Log stdout to find crasheseditttcn3-pgw-test/jenkins.sh
- ttcn3-pgw-test/open5gs-upf.yamlttcn3-pgw-test/open5gs-nrf.yamlttcn3-pgw-test/open5gs-smf.yamlca3b751ae0cea47aa911415e6ba77fb1daf0a62e1649353331000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-pgw-test: Use process name in log file
This way it becomes similar to what we use in ttcn3-ggsn-tests-ogs.
Change-Id: Ibac0e6bc9dc7c2e576a4f5d1ccb730211d1e1427
2022-04-07 19:42:11 +0200ca3b751ae0cea47aa911415e6ba77fb1daf0a62ettcn3-pgw-test: Use process name in log fileeditttcn3-pgw-test/open5gs-upf.yamleditttcn3-pgw-test/open5gs-nrf.yamleditttcn3-pgw-test/open5gs-smf.yaml
- ttcn3-ggsn-test/jenkins-ogs.shttcn3-pgw-test/jenkins.sh6acec0cbd134ca93567fd7fbf8a74ea9351e44631649353731000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-{pgw,ggsn}-tests: Add comment with procedure to get open5gs-smfd bt automatically
Some specific gdb commands need to be run in open5gs-smfd to get the
desired result (some signals need to be ignored).
gdb use is not enabled by default. Furthermore, if one wants to use it,
editing the Dockerfile to install gdb is required.
Change-Id: I1ac8b77e84d57040fc09964356bc8a01e5d721e3
2022-04-07 19:48:51 +02006acec0cbd134ca93567fd7fbf8a74ea9351e4463ttcn3-{pgw,ggsn}-tests: Add comment with procedure to get open5gs-smfdeditttcn3-ggsn-test/jenkins-ogs.sheditttcn3-pgw-test/jenkins.sh
- ttcn3-pgw-test/upfd-setup.shttcn3-pgw-test/upfd.shttcn3-pgw-test/open5gs-smf.yamlttcn3-pgw-test/ogstun-setup.shttcn3-pgw-test/open5gs-upf.yamlttcn3-pgw-test/jenkins.sh5c9182751cd6a9ea24ac81a48ccda12fb59d5a831649355858000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-pgw-tests: use same bootstrap for upfd as in ttcn-ggsn-tests-ogs
This approach has several benefits:
* We end up with ip/tun setup output in the same log file as
open5gs-upfd process output.
* We configure all ip/tun *before* the open5gs-upfd process starts.
Furthermore, we have same procedure as in ttcn3-ggsn-tests-ogs, which
simplifies maintainment/use.
The IP address pool for UEs is still different in pgw-tests and
ggsn-tests-ogs. We can make them the same in subsequent patches.
Change-Id: I94219abbeb5e004ce707407b5aa5ee8ad6c3a80e
2022-04-07 20:24:18 +02005c9182751cd6a9ea24ac81a48ccda12fb59d5a83ttcn3-pgw-tests: use same bootstrap for upfd as in ttcn-ggsn-tests-ogseditttcn3-pgw-test/open5gs-upf.yamladdttcn3-pgw-test/upfd-setup.sheditttcn3-pgw-test/jenkins.sheditttcn3-pgw-test/open5gs-smf.yamldeletettcn3-pgw-test/ogstun-setup.shaddttcn3-pgw-test/upfd.sh
- ttcn3-pgw-test/jenkins.sh9a744f21082ddd32083e5ed685aa124512d390ba1649356711000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-pgw-test: Log open5gs-nrfd stdout/stderr
This way we see potential crashes.
Change-Id: I31f2ff2dd5daa68756e910c4cb91acefdad50cb1
2022-04-07 20:38:31 +02009a744f21082ddd32083e5ed685aa124512d390battcn3-pgw-test: Log open5gs-nrfd stdout/stderreditttcn3-pgw-test/jenkins.sh
- ttcn3-pgw-test/open5gs-smf.yamlttcn3-pgw-test/open5gs-upf.yamlttcn3-pgw-test/open5gs-nrf.yamlttcn3-ggsn-test/ogs/open5gs-smf.yamlttcn3-ggsn-test/ogs/open5gs-upf.yaml713468b295cf55e77058b01ea6100047b3739a0f1649356812000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-{ggsn,pgw}-test: Avoid open5gs itself logging to a file
We already log stdout/stderr to a file, so there's no need to log a file
internally. We prefer logging that through stdout/stderr in order to
catch more stuff, like segfaults.
Change-Id: Ifdc010f26abdc8cefeec0c72a1f617911ec375d7
2022-04-07 20:40:12 +0200713468b295cf55e77058b01ea6100047b3739a0fttcn3-{ggsn,pgw}-test: Avoid open5gs itself logging to a fileeditttcn3-pgw-test/open5gs-nrf.yamleditttcn3-ggsn-test/ogs/open5gs-smf.yamleditttcn3-pgw-test/open5gs-upf.yamleditttcn3-pgw-test/open5gs-smf.yamleditttcn3-ggsn-test/ogs/open5gs-upf.yaml
githttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol