Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/docker-playground/+/29355 )
Change subject: osmo-hnbgw-master: build with --enable-pfcp
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> I would really enable pfcp by default at some point near in time.
it was discussed before with a different conclusion
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/29355
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: If84261cba2bf3b75c454fd5d16fd19a88a468eb7
Gerrit-Change-Number: 29355
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 15 Sep 2022 12:53:09 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: osmith, pespin.
Hello osmith, Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/docker-playground/+/29339
to look at the new patch set (#4).
Change subject: add ttcn3-hnbgw-test variant with-pfcp
......................................................................
add ttcn3-hnbgw-test variant with-pfcp
Run HNBGW tests a second time with PFCP enabled. Just run all the same
tests again, no matter if they are related to PS RAB Assignment or not,
to also ensure no ill side effects from PFCP configuration.
Related: SYS#5895
Depends: I511e758807e0512c18f3f9e0a8c4699b9a3f5992 (osmo-ttcn3-hacks)
Change-Id: I02b60941343000a4618e95f56326bec170c32bfe
---
M ttcn3-hnbgw-test/jenkins.sh
A ttcn3-hnbgw-test/with-pfcp/HNBGW_Tests.cfg
A ttcn3-hnbgw-test/with-pfcp/osmo-hnbgw.cfg
3 files changed, 164 insertions(+), 44 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/docker-playground refs/changes/39/29339/4
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/29339
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I02b60941343000a4618e95f56326bec170c32bfe
Gerrit-Change-Number: 29339
Gerrit-PatchSet: 4
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: osmith, pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/docker-playground/+/29339 )
Change subject: add ttcn3-hnbgw-test variant with-pfcp
......................................................................
Patch Set 3:
(1 comment)
File ttcn3-hnbgw-test/jenkins.sh:
https://gerrit.osmocom.org/c/docker-playground/+/29339/comment/f5d5a5cb_f63…
PS3, Line 82: echo Starting container with STP
> If you want to understand what's run here, and how run a subset of the things here: yes it helps a l […]
running with gdb in the jenkins.sh?
i still disagree that it helps at all nor that it's worth the effort but if it makes your day and if we can stop ping ponging on bikesheds in a jenkins ci shell script that could hardly be more obscure in the first place even without indirection of calling functions with parameters... hrm.
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/29339
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I02b60941343000a4618e95f56326bec170c32bfe
Gerrit-Change-Number: 29339
Gerrit-PatchSet: 3
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 15 Sep 2022 12:25:11 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: osmith.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/29359 )
Change subject: lint: ignore MACRO_WITH_FLOW_CONTROL
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
i have made one too, OSMO_NAME_C_IMPL(), but still i think it's ok to let the linter complain about it. because in general we should avoid flow control macros, and for the very rare cases where we allow it, it should be good enough to find someone to remove the linter vote before merging
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/29359
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I79da5a426db59031e3b16aecedeaa1498c91e847
Gerrit-Change-Number: 29359
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 15 Sep 2022 12:06:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: laforge, pespin, msuraev, dexter.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/28846 )
Change subject: Make esme struct shared
......................................................................
Patch Set 21:
(2 comments)
File include/osmocom/smpp/smpp.h:
https://gerrit.osmocom.org/c/osmo-msc/+/28846/comment/5e997766_64e5457e
PS21, Line 14: esme
You marked my comment as resolved without responding.
struct naming seems unclear; we now have struct esme and struct smpp_esme, right? api doc explanation of the difference would be good
File src/utils/Makefile.am:
https://gerrit.osmocom.org/c/osmo-msc/+/28846/comment/57114f65_ac22c05a
PS19, Line 45: $(top_builddir)/src/libvlr/libvlr.a \
> I completely agree - this problems dates back to BSC/MSC split and the shared gsm_network struct whi […]
struct gsm_network contains opaque pointers to vlr_instance, that shouldn't pull in libvlr as dependency; is it gsm_network_init()? this is not so important, but seems like an easy way out here
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28846
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I8f7ac2c00d16660925dd0b03aa1a0973edf9eb70
Gerrit-Change-Number: 28846
Gerrit-PatchSet: 21
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 15 Sep 2022 12:01:15 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: msuraev <msuraev(a)sysmocom.de>
Gerrit-MessageType: comment