Attention is currently required from: laforge.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-abis/+/30375 )
Change subject: trau_sync: Add the V.110 sync pattern
......................................................................
Patch Set 2:
(1 comment)
File include/osmocom/trau/trau_sync.h:
https://gerrit.osmocom.org/c/libosmo-abis/+/30375/comment/7847b092_2254a65e
PS2, Line 5: enum osmo_tray_sync_pat_id {
> can't do in a backwards compatible way. It's part of public API and osmo-mgw uses it. […]
I'd do #define osmo_tray_sync_pat_id osmo_trau_sync_pat_id for backward compat and change the name. Let's not keep typos in API further in the future.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/30375
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: I3aab5c3f494f6ea2b11f3cf69fb09bc77ea941d8
Gerrit-Change-Number: 30375
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Wed, 30 Nov 2022 17:00:58 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ci/+/30394 )
Change subject: jobs/osmocom-release-tarballs: use any node
......................................................................
jobs/osmocom-release-tarballs: use any node
Prepare to retire build2-deb9build-ansible. With changes in the script,
it doesn't need a persistent workspace anymore, it skips building source
tarballs if they exist on the remote server.
Depends: docker-playground I4b8c149c9cdbe7c613eea5d9be15794de5e5ddce
Related: OS#5793
Change-Id: If56614caaa9c0c44419af596451d48c1970e9014
---
M jobs/osmocom-release-tarballs.yml
1 file changed, 1 insertion(+), 4 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/94/30394/1
diff --git a/jobs/osmocom-release-tarballs.yml b/jobs/osmocom-release-tarballs.yml
index ee83ea4..458cd6d 100644
--- a/jobs/osmocom-release-tarballs.yml
+++ b/jobs/osmocom-release-tarballs.yml
@@ -29,12 +29,9 @@
url: https://gerrit.osmocom.org/docker-playground
git-config-name: 'Jenkins Builder'
git-config-email: 'jenkins(a)osmocom.org'
- # Don't wipe workspace to keep generated release tarballs
- wipe-workspace: false
+ wipe-workspace: true
triggers:
- timed: "@midnight"
- # Limit to one specific builder (so we don't regenerate all tarballs when switching to another builder)
- node: build2-deb9build-ansible
publishers:
- email:
notify-every-unstable-build: true
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/30394
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: If56614caaa9c0c44419af596451d48c1970e9014
Gerrit-Change-Number: 30394
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newchange
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ci/+/30390 )
Change subject: scripts/osmocom-build-old…: skip openbsc 1.4.{0,1}
......................................................................
scripts/osmocom-build-old…: skip openbsc 1.4.{0,1}
Don't attempt to build openbsc 1.4.0 and 1.4.1 in the
osmocom-build-old-tags-against-master job, as it fails to build with a
modern gcc with a potential null pointer dereference warning that gets
treated as error. This was fixed in 1.4.2 with openbsc patch
I93d816a20ba208e9fd32a1fc172a78ccd326e1ba.
A more modern gcc gets used, as this job gets changed to not only run on
jenkins nodes with debian 9 installed, but also more modern versions.
This job does not run in docker, and since it still passes it doesn't
seem worth changing that now.
Related: OS#5793
Change-Id: Ibf4b66195fbd70a68d63929b156a9aac54a699bc
---
M scripts/osmocom-build-old-tags-against-master.sh
1 file changed, 2 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/90/30390/1
diff --git a/scripts/osmocom-build-old-tags-against-master.sh b/scripts/osmocom-build-old-tags-against-master.sh
index 71d5a1f..b6e6138 100755
--- a/scripts/osmocom-build-old-tags-against-master.sh
+++ b/scripts/osmocom-build-old-tags-against-master.sh
@@ -54,6 +54,8 @@
echo "1.0.0" # testsuite
echo "1.3.1" # testsuite: libosmocore 6407c822ae0d45d047deb0dff095f028a90c1ecc
echo "1.3.2" # testsuite: libosmocore 6407c822ae0d45d047deb0dff095f028a90c1ecc
+ echo "1.4.0" # error: potential null pointer dereference, fixed in 1.4.2
+ echo "1.4.1" # error: potential null pointer dereference, fixed in 1.4.2
;;
osmo-bsc)
# Depends on libosmo-legacy-mgcp, but missing LIBOSMOLEGACYMGCP_CFLAGS so we can't build it with
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/30390
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: Ibf4b66195fbd70a68d63929b156a9aac54a699bc
Gerrit-Change-Number: 30390
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newchange
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ci/+/30391 )
Change subject: jobs: don't set node where it doesn't make sense
......................................................................
jobs: don't set node where it doesn't make sense
Remove the node attribute as these can run on any node. I've configured
the three deb11 nodes with "Usage: Use this node as much as possible"
instead of previously "Only build jobs with label expression matching
this node", so simply not specifying a node is now possible. Previously
it wouldn't have any node to run on as all of them were configured that
way.
Related: OS#5793
Change-Id: I2d67daf1cc7930649d097af23c18990cc3ae55fd
---
M jobs/osmo-gsm-manuals-trigger.yml
M jobs/registry-triggers.yml
2 files changed, 0 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/91/30391/1
diff --git a/jobs/osmo-gsm-manuals-trigger.yml b/jobs/osmo-gsm-manuals-trigger.yml
index bbb883f..0fca5a7 100644
--- a/jobs/osmo-gsm-manuals-trigger.yml
+++ b/jobs/osmo-gsm-manuals-trigger.yml
@@ -15,7 +15,6 @@
Roll out osmo-gsm-manuals to relevant build environments.<br>
<br>
Related: <a href="https://osmocom.org/issues/4912">OS#4912</a>
- node: osmocom-master-debian9
scm:
- git:
url: https://gerrit.osmocom.org/osmo-gsm-manuals
diff --git a/jobs/registry-triggers.yml b/jobs/registry-triggers.yml
index dcdde85..823062b 100644
--- a/jobs/registry-triggers.yml
+++ b/jobs/registry-triggers.yml
@@ -12,7 +12,6 @@
name: 'registry-trigger-{repos}'
description: |
Update registry.osmocom.org after changes in {repos}.
- node: osmocom-master-debian9
scm:
- git:
url: https://gerrit.osmocom.org/{repos}
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/30391
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I2d67daf1cc7930649d097af23c18990cc3ae55fd
Gerrit-Change-Number: 30391
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: pespin.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-abis/+/30375 )
Change subject: trau_sync: Add the V.110 sync pattern
......................................................................
Patch Set 2:
(1 comment)
File include/osmocom/trau/trau_sync.h:
https://gerrit.osmocom.org/c/libosmo-abis/+/30375/comment/409c480e_68c14b5f
PS2, Line 5: enum osmo_tray_sync_pat_id {
> did you see this typo here? "tray". […]
can't do in a backwards compatible way. It's part of public API and osmo-mgw uses it. Well, one could rename it and add a #define for source compatibility, but I'm wondering if it's really worth it and whether we might still get some fall-out?
--
To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/30375
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: I3aab5c3f494f6ea2b11f3cf69fb09bc77ea941d8
Gerrit-Change-Number: 30375
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
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: Wed, 30 Nov 2022 16:48:31 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment