January 2025 - gerrit-log - lists.osmocom.org

[XS] Change in osmo-ci[master]: ansible: coverity: fix creating symlink

by osmith

osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ci/+/39341?usp=email ) Change subject: ansible: coverity: fix creating symlink ...................................................................... ansible: coverity: fix creating symlink Fix for: Unsupported parameters for (ansible.legacy.command) module: warn. Supported parameters include: _raw_params, _uses_shell, argv, chdir, creates, executable, expand_argument_vars, removes, stdin, stdin_add_newline, strip_empty_ends. Fixes: OS#6702 Change-Id: I42be62cbba38a2a33ebe46fa1094155358490383 --- M ansible/roles/install-coverity/tasks/main.yml 1 file changed, 0 insertions(+), 2 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/41/39341/1 diff --git a/ansible/roles/install-coverity/tasks/main.yml b/ansible/roles/install-coverity/tasks/main.yml index ca4a24c..0d43a27 100644 --- a/ansible/roles/install-coverity/tasks/main.yml +++ b/ansible/roles/install-coverity/tasks/main.yml @@ -38,8 +38,6 @@ - name: create link /opt/coverity/current shell: rm -vf /opt/coverity/current && ln -svf /opt/coverity/{{ coverity_version }}/* /opt/coverity/current - args: - warn: false when: coverity_copy.failed == False - name: "Please download {{ coverity_installer_file }} to your ansible directory to allow ansible to install coverity" -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/39341?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: I42be62cbba38a2a33ebe46fa1094155358490383 Gerrit-Change-Number: 39341 Gerrit-PatchSet: 1 Gerrit-Owner: osmith <osmith(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[S] Change in osmo-ci[master]: ansible: coverity: improve file not found error

by osmith

osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ci/+/39342?usp=email ) Change subject: ansible: coverity: improve file not found error ...................................................................... ansible: coverity: improve file not found error Abort early when the coverity tarball was not found and tell the user where they can download it, and where exactly the file needs to be. Change-Id: Iddf629abd5c5a87afc238fbf6927cda9aa6f49b2 --- M ansible/roles/install-coverity/tasks/main.yml 1 file changed, 5 insertions(+), 8 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/42/39342/1 diff --git a/ansible/roles/install-coverity/tasks/main.yml b/ansible/roles/install-coverity/tasks/main.yml index 0d43a27..7dc3043 100644 --- a/ansible/roles/install-coverity/tasks/main.yml +++ b/ansible/roles/install-coverity/tasks/main.yml @@ -23,24 +23,21 @@ register: coverity_copy ignore_errors: yes + - name: coverity download hint + ansible.builtin.fail: + msg: "Login and download {{ coverity_installer_file }} from https://scan.coverity.com/download (Linux64) and put it into osmo-ci/ansible/files." + when: coverity_copy.failed == True + - name: create /opt/coverity/{{ coverity_version }}/ file: path: /opt/coverity/{{ coverity_version }}/ state: directory - when: coverity_copy.failed == False - name: unpack coverity unarchive: src: "/tmp/{{ coverity_installer_file }}" dest: /opt/coverity/{{ coverity_version }} remote_src: yes - when: coverity_copy.failed == False - name: create link /opt/coverity/current shell: rm -vf /opt/coverity/current && ln -svf /opt/coverity/{{ coverity_version }}/* /opt/coverity/current - when: coverity_copy.failed == False - - - name: "Please download {{ coverity_installer_file }} to your ansible directory to allow ansible to install coverity" - debug: - msg: "Ansible can not find {{ coverity_installer_file }}" - when: coverity_copy.failed -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/39342?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: Iddf629abd5c5a87afc238fbf6927cda9aa6f49b2 Gerrit-Change-Number: 39342 Gerrit-PatchSet: 1 Gerrit-Owner: osmith <osmith(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[XS] Change in libosmocore[master]: osmo_io: iofd_msgb_alloc(): Allow allocating msgb of len=0xffff

by pespin

Attention is currently required from: fixeria, osmith. pespin has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/libosmocore/+/39325?usp=email ) Change subject: osmo_io: iofd_msgb_alloc(): Allow allocating msgb of len=0xffff ...................................................................... Patch Set 1: (1 comment) Patchset: PS1: This should go into a patch release. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/39325?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I6f9125916a301414301587f84fc3db98549a2f3f Gerrit-Change-Number: 39325 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-CC: Jenkins Builder Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Wed, 15 Jan 2025 15:50:09 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No

5 months, 1 week

1
0
0 0

[XS] Change in osmo-pcap[master]: server: Limit rx buffer size to UINT16_MAX

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-pcap/+/39340?usp=email ) Change subject: server: Limit rx buffer size to UINT16_MAX ...................................................................... server: Limit rx buffer size to UINT16_MAX We can't receive bigger buffers anyway as limited by protocol and msgb itself, so trim it. Change-Id: I96bfe1625510cca67f5781e2895caf2a3612ec62 --- M src/osmo_server_core.c 1 file changed, 3 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-pcap refs/changes/40/39340/1 diff --git a/src/osmo_server_core.c b/src/osmo_server_core.c index f6c42ce..14a1410 100644 --- a/src/osmo_server_core.c +++ b/src/osmo_server_core.c @@ -149,6 +149,9 @@ pcapng_max_len_opt + sizeof(uint32_t); data_max_len = OSMO_MAX(data_max_len, pcapng_epb_max_len + server->max_snaplen); + + /* We are limited by (struct osmo_pcap_data)->len and msgb->len being uint16: */ + data_max_len = OSMO_MIN(data_max_len, UINT16_MAX); return data_max_len; } -- To view, visit https://gerrit.osmocom.org/c/osmo-pcap/+/39340?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-pcap Gerrit-Branch: master Gerrit-Change-Id: I96bfe1625510cca67f5781e2895caf2a3612ec62 Gerrit-Change-Number: 39340 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[M] Change in osmocom-bb[master]: trx_toolkit/clck_gen.py: Fix clock generator not to accumulate timing...

by fixeria

fixeria has submitted this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/39327?usp=email ) Change subject: trx_toolkit/clck_gen.py: Fix clock generator not to accumulate timing error ...................................................................... trx_toolkit/clck_gen.py: Fix clock generator not to accumulate timing error CLCKGen currently works as follows: sleep(ctr_interval) some work sleep(ctr_interval) some work sleep(ctr_interval) some work ... The intent here is to do some work at timestamps that are multiple of ctr_interval, however the implementation does not match the intent, because 1) sleep(ctr_interval) is not guaranteed by the OS to be ideal, so there will always be some jitter in actually slept time without any guarantee that the error will fluctuate over zero without accumulating. 2) "some work" takes some time to run and that time adds again and again to the current time when next sleep(ctr_interval) starts. As the result even if sleep implementation would be ideal, then n'th sleep would start not at t₀ + n·ctr_interval but instead at t₀ + n·ctr_interval + Σ1..n t(work_i) where trailing Σ term adds over and over as the timing error which can be seen as e.g. increasing trend of received GSM clock jitter in https://osmocom.org/issues/4658#note-10 . The thinko in the clock generator logic is not so much visible if "some work" takes only a bit of time or is done infrequently. That was actually the case before fake_trx added tx queueing in 6e1c82d2 (trx_toolkit/transceiver.py: implement the transmit burst queue) because before that commit some work was only "send IND CLOCK data every ~ 100th tick". However after 6e1c82d2 the work was adjusted to do linear scan of tx queue over and over at every tick which amplified error accumulation and highlighted the problem. With that tx queuing in fake_trx was disabled in d4ed09df (Revert "trx_toolkit/transceiver.py: implement the transmit burst queue") with the rationale being most likely, as https://osmocom.org/issues/4658#note-10 says, Unfortunately, Python is not fast enough to handle the queues in time. Despite the relatively low CPU usage, fake_trx.py fails to scheduler everything during one TDMA frame period. This causes some of our TTCN-3 test cases to fail. ... Most likely, the problem is that Python's threading.Event is not accurate enough. Running with SCHED_RR does not change anything. However with the above analysis we can see that it is the logic in CLCKgen that needs fixing, not threading.Event . For the reference threading.Event indeed used dumb timeout implementation on Python2: https://github.com/python/cpython/blob/2.7-0-g8d21aa21f2c/Lib/threading.py#… https://github.com/python/cpython/blob/2.7-0-g8d21aa21f2c/Lib/threading.py#… but on Python3 it essentially uses plain Lock.acquire(timeout) which, under the hood, uses PyThread_acquire_lock_timed - a plain wrapper over sem_timedwait: https://github.com/python/cpython/blob/v3.11.9-9-g1b0e63c81b5/Lib/threading… https://github.com/python/cpython/blob/v3.11.9-9-g1b0e63c81b5/Modules/_thre… https://github.com/python/cpython/blob/v3.11.9-9-g1b0e63c81b5/Python/thread… so at least with py3 there should be no question about threading.Event . -> Fix timing error accumulation by reworking the clock generator loop to compensate observed jitter, caused by OS noise and the work taking time, by adjusting to-sleep δt each tick accordingly. This is generally good for correctness and will allow us to reinstate tx queueing in fake_trx. Without the fix added test fails as FAIL: test_no_timing_error_accumulated (test_clck_gen.CLCKGen_Test.test_no_timing_error_accumulated) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/kirr/src/osmocom/bb/src/target/trx_toolkit/test_clck_gen.py", line 60, in test_no_timing_error_accumulated self.assertTrue((ntick+1)*clck.ctr_interval > δT, "tick #%d: time overrun by %dµs total" % AssertionError: False is not true : tick #200: time overrun by 572478µs total Change-Id: I928801422c9af80c368261f617b91d7ecfedbabf Related: OS#4658, OS#6672 --- M src/target/trx_toolkit/clck_gen.py A src/target/trx_toolkit/test_clck_gen.py 2 files changed, 87 insertions(+), 1 deletion(-) Approvals: Jenkins Builder: Verified fixeria: Looks good to me, approved pespin: Looks good to me, but someone else must approve laforge: Looks good to me, but someone else must approve diff --git a/src/target/trx_toolkit/clck_gen.py b/src/target/trx_toolkit/clck_gen.py index 427eb88..15b653f 100755 --- a/src/target/trx_toolkit/clck_gen.py +++ b/src/target/trx_toolkit/clck_gen.py @@ -22,6 +22,7 @@ import logging as log import threading +import time import signal from app_common import ApplicationBase @@ -85,7 +86,24 @@ self._breaker.clear() def _worker(self): - while not self._breaker.wait(self.ctr_interval): + # run .send_clck_ind() every .ctr_interval + # be careful not to accumulate timing error when organizing the clock loop + ns = 1e-9 + us = 1e-6 + t_tick = int(self.ctr_interval // ns) + t_next = time.monotonic_ns() + while 1: + t_next += t_tick + t = time.monotonic_ns() + dt = (t_next - t) + if dt < 0: + log.warning("CLCKGen: time overrun by %dus; resetting the clock" % (dt * ns // us)) + t_next = time.monotonic_ns() + dt = 0 + + if self._breaker.wait(dt * ns): + break + self.send_clck_ind() def send_clck_ind(self): diff --git a/src/target/trx_toolkit/test_clck_gen.py b/src/target/trx_toolkit/test_clck_gen.py new file mode 100644 index 0000000..a920ce1 --- /dev/null +++ b/src/target/trx_toolkit/test_clck_gen.py @@ -0,0 +1,68 @@ +#!/usr/bin/env python3 +# -*- coding: utf-8 -*- + +# TRX Toolkit +# Unit test for CLCKGen +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. + +import threading +import time +import unittest + +import clck_gen + + +class CLCKGen_Test(unittest.TestCase): + + # verify that timing error is not accumulated in the clock gen loop + def test_no_timing_error_accumulated(self): + # observe many ticks with spending some noticeable time in clock handler each tick + # assert that t(last) - t(first) ≈ ntick·dt(tick) + # this will break if the clock generator is not careful to prevent timing error from accumulating + clck = clck_gen.CLCKGen([]) + ntick = 200 # ~ 1 s + tick = 0 + tstart = tend = None + done = threading.Event() + + def _(fn): + nonlocal tick, tstart, tend + if tick == 0: + tstart = time.monotonic() + if tick == ntick: + tend = time.monotonic() + done.set() + tick += 1 + time.sleep(clck.ctr_interval / 2) + clck.clck_handler = _ + + clck.start() + try: + ok = done.wait(10) + self.assertTrue(ok, "clck_gen stuck") + + self.assertIsNotNone(tstart) + self.assertIsNotNone(tend) + dT = tend - tstart + dTok = ntick * clck.ctr_interval + dTerr = dT - dTok + self.assertTrue((ntick-1)*clck.ctr_interval < dT, "tick #%d: time underrun by %dus total" % + (ntick, dTerr // 1e-6)) + self.assertTrue((ntick+1)*clck.ctr_interval > dT, "tick #%d: time overrun by %dus total" % + (ntick, dTerr // 1e-6)) + + finally: + clck.stop() + + +if __name__ == '__main__': + unittest.main() -- To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/39327?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: osmocom-bb Gerrit-Branch: master Gerrit-Change-Id: I928801422c9af80c368261f617b91d7ecfedbabf Gerrit-Change-Number: 39327 Gerrit-PatchSet: 2 Gerrit-Owner: kirr <kirr(a)nexedi.com> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: osmith <osmith(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[M] Change in osmocom-bb[master]: trx_toolkit/clck_gen.py: Fix clock generator not to accumulate timing...

by fixeria

Attention is currently required from: kirr, osmith. fixeria has posted comments on this change by kirr. ( https://gerrit.osmocom.org/c/osmocom-bb/+/39327?usp=email ) Change subject: trx_toolkit/clck_gen.py: Fix clock generator not to accumulate timing error ...................................................................... Patch Set 2: Code-Review+2 (1 comment) Patchset: PS1: > Looking forward to your review. Hope it will be ok, but let's see. The patch looks good to me, LGTM. Thanks again! -- To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/39327?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmocom-bb Gerrit-Branch: master Gerrit-Change-Id: I928801422c9af80c368261f617b91d7ecfedbabf Gerrit-Change-Number: 39327 Gerrit-PatchSet: 2 Gerrit-Owner: kirr <kirr(a)nexedi.com> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: osmith <osmith(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Attention: kirr <kirr(a)nexedi.com> Gerrit-Comment-Date: Wed, 15 Jan 2025 15:33:45 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: osmith <osmith(a)sysmocom.de> Comment-In-Reply-To: kirr <kirr(a)nexedi.com> Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[XS] Change in osmo-ci[master]: ansible: build5-deb12build is also a coverity builder

by osmith

osmith has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/39333?usp=email ) Change subject: ansible: build5-deb12build is also a coverity builder ...................................................................... ansible: build5-deb12build is also a coverity builder Change-Id: Id9d35658197409bcaba3e267cab36d7aa2a28972 --- M ansible/hosts 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: pespin: Looks good to me, but someone else must approve osmith: Looks good to me, approved Jenkins Builder: Verified diff --git a/ansible/hosts b/ansible/hosts index d3c59d6..57966d3 100644 --- a/ansible/hosts +++ b/ansible/hosts @@ -4,6 +4,7 @@ [coverity_slaves] build4-deb12build-ansible ansible_host=2a01:4f8:121:200a::1:3 +build5-deb12build-ansible ansible_host=2a01:4f8:140:926a::1:3 [jenkins_slaves] build4-deb12build-ansible ansible_host=2a01:4f8:121:200a::1:3 osmocom_jenkins_slave_fstrim=True docker_max_image_space="50 GB" -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/39333?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: Id9d35658197409bcaba3e267cab36d7aa2a28972 Gerrit-Change-Number: 39333 Gerrit-PatchSet: 2 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[XS] Change in osmo-ci[master]: update coverity version to 2024.6.1 (current one)

by osmith

osmith has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/39332?usp=email ) Change subject: update coverity version to 2024.6.1 (current one) ...................................................................... update coverity version to 2024.6.1 (current one) coverity started to reject builds with older versions Change-Id: Ifa5621279bbf14839096e10ced74ed855908897b --- M ansible/roles/install-coverity/defaults/main.yml 1 file changed, 1 insertion(+), 1 deletion(-) Approvals: osmith: Looks good to me, approved Jenkins Builder: Verified pespin: Looks good to me, but someone else must approve diff --git a/ansible/roles/install-coverity/defaults/main.yml b/ansible/roles/install-coverity/defaults/main.yml index 7be5be6..1176fab 100644 --- a/ansible/roles/install-coverity/defaults/main.yml +++ b/ansible/roles/install-coverity/defaults/main.yml @@ -1,4 +1,4 @@ --- -coverity_version: 2023.6.2 +coverity_version: 2024.6.1 coverity_installer_file: "cov-analysis-linux64-{{ coverity_version }}.tar.gz" -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/39332?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: Ifa5621279bbf14839096e10ced74ed855908897b Gerrit-Change-Number: 39332 Gerrit-PatchSet: 2 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>

5 months, 1 week

1
0
0 0

[XS] Change in osmo-ci[master]: ansible: build5-deb12build is also a coverity builder

by osmith

Attention is currently required from: laforge. osmith has posted comments on this change by laforge. ( https://gerrit.osmocom.org/c/osmo-ci/+/39333?usp=email ) Change subject: ansible: build5-deb12build is also a coverity builder ...................................................................... Patch Set 1: (1 comment) Patchset: PS1: I'll merge these for fixing https://osmocom.org/issues/6702 on top -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/39333?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: Id9d35658197409bcaba3e267cab36d7aa2a28972 Gerrit-Change-Number: 39333 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Comment-Date: Wed, 15 Jan 2025 15:20:55 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No

5 months, 1 week

1
0
0 0

[M] Change in osmo-bsc[master]: nokia_site: add object_type, object_state and reset_type

by pespin

Attention is currently required from: csaba.sipos. pespin has posted comments on this change by csaba.sipos. ( https://gerrit.osmocom.org/c/osmo-bsc/+/39315?usp=email ) Change subject: nokia_site: add object_type, object_state and reset_type ...................................................................... Patch Set 1: (1 comment) Patchset: PS1: > Hi Pau, […] Put it together in the same patch with the code using it. -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/39315?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: I0f31cd711768c963e5c14c0f4969ff76cb05c12b Gerrit-Change-Number: 39315 Gerrit-PatchSet: 1 Gerrit-Owner: csaba.sipos <metro4(a)freemail.hu> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Attention: csaba.sipos <metro4(a)freemail.hu> Gerrit-Comment-Date: Wed, 15 Jan 2025 15:20:31 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: csaba.sipos <metro4(a)freemail.hu>

5 months, 1 week

1
0
0 0

2025

2024

2023

2022

gerrit-log January 2025