laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/dahdi-tools/+/34013 )
Change subject: Initial support for trunkdev
......................................................................
Patch Set 1: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/c/dahdi-tools/+/34013
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: dahdi-tools
Gerrit-Branch: master
Gerrit-Change-Id: Ie05100c80fd978e7ac6f5a028e0ef6c828e0bcc3
Gerrit-Change-Number: 34013
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Fri, 25 Aug 2023 09:28:00 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: wbokslag.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-tetra/+/34169 )
Change subject: Added crypto support
......................................................................
Patch Set 2: Code-Review+1
(1 comment)
File src/crypto/tetra_crypto.c:
https://gerrit.osmocom.org/c/osmo-tetra/+/34169/comment/8872d3dd_d9c6bc04
PS2, Line 249: // key->addr, key->index, tcs->hn, tetra_tdma_time_dump(tdma_time), tmpdu_offset, ct_len);
why is this (and similar lines below) commented-out in this patch? I'd suspect it would work just as well irrespective of crypto being introduced? So it looks like a logically separate change to me.
In general, we might benefit from introducing proper libosmocore log sub-systems in osmo-tetra, where each sub-system can have a differnt log level etc. - not asking you to work on this, just sharing general perspective.
--
To view, visit https://gerrit.osmocom.org/c/osmo-tetra/+/34169
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-tetra
Gerrit-Branch: master
Gerrit-Change-Id: I0c0227cf5b747bd5032602390175b898173f6ae6
Gerrit-Change-Number: 34169
Gerrit-PatchSet: 2
Gerrit-Owner: wbokslag <w.bokslag(a)midnightblue.nl>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: wbokslag <w.bokslag(a)midnightblue.nl>
Gerrit-Comment-Date: Fri, 25 Aug 2023 09:27:15 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: laforge.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/34201 )
Change subject: contrib/jenkins-build: libosmocore: disable-uring
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> I would think it makes more sense to have liburing-dev available at build time than to explicitly di […]
It is available in e.g. debian-bookworm-build. The problem with the osmo-gsm-tester build jobs is that they don't run in docker yet as I just learned (I was assuming that by now we already migrated all of them to run in docker). I think we should migrate them as well, but that's a larger effort and given that we don't maintain osmo-gsm-tester much right now besides keeping osmo-gsm-tester_virtual functional I wrote the patch here to just use --disable-uring.
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/34201
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-tester
Gerrit-Branch: master
Gerrit-Change-Id: Ibc9605933380351a5fd23b772868c0e698b39c37
Gerrit-Change-Number: 34201
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Fri, 25 Aug 2023 09:24:37 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: osmith, dexter.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/pysim/+/34155 )
Change subject: sim-reset-server: fix error printing sw_match_error
......................................................................
Patch Set 2:
(1 comment)
File contrib/sim-rest-server.py:
https://gerrit.osmocom.org/c/pysim/+/34155/comment/44f3b06a_26887035
PS1, Line 104: failure.value
> Unfortunately str(failure.value) didn't fix the problem. That was one of the things I tried before. […]
I think you need a __str__ method on the object in order for str() to work. What is the object/type of failure.value when it fails?
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/34155
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I5a1d19abeb00c2c9dc26517abc44a5c916f2d658
Gerrit-Change-Number: 34155
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 25 Aug 2023 09:23:17 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: osmith.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/34201 )
Change subject: contrib/jenkins-build: libosmocore: disable-uring
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
Patchset:
PS1:
I would think it makes more sense to have liburing-dev available at build time than to explicitly disable building uring support everywhere.
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/34201
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-tester
Gerrit-Branch: master
Gerrit-Change-Id: Ibc9605933380351a5fd23b772868c0e698b39c37
Gerrit-Change-Number: 34201
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 25 Aug 2023 09:21:36 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/34201 )
Change subject: contrib/jenkins-build: libosmocore: disable-uring
......................................................................
Patch Set 1: Verified+1
(1 comment)
This change is ready for review.
Patchset:
PS1:
The patch fixes the failures, I've pushed it to osmith/wip and ran the jobs: https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/
gerrit verifications are failing for a different reason (https://osmocom.org/issues/6149), so I'll override it for this patch.
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/34201
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-tester
Gerrit-Branch: master
Gerrit-Change-Id: Ibc9605933380351a5fd23b772868c0e698b39c37
Gerrit-Change-Number: 34201
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 25 Aug 2023 09:15:08 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment