laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/34645?usp=email )
Change subject: scripts/docker-cleanup: remove containers > 24h
......................................................................
scripts/docker-cleanup: remove containers > 24h
Remove containers starting with jenkins- or having ttcn3 in the name, if
they have been running for more than 24 hours. This can happen with the
ttcn3 testsuites, as they typically start multiple docker containers in
the background (one per Osmocom program) before they start the testsuite
docker container in the foreground. Usually the clean up trap makes sure
that all containers get killed, but we have seen that a few containers
have been running for a few months. One reason for this could be
temporary loss of connection between the jenkins server and the node
running the job.
Extend the clean script to remove the containers that were not properly
removed by the clean up trap.
Historically we used to kill docker containers of the same name before
starting a testsuite, but this had the downside that we could not start
the same testsuite multiple times in parallel. This was refactored in
docker-playground Ifcd384272c56d585e220e2588f2186dc110902ed.
Change-Id: I58c17b57c998eaba411658e83b7295d7cfcf9a23
---
M scripts/docker-cleanup.sh
1 file changed, 61 insertions(+), 0 deletions(-)
Approvals:
Jenkins Builder: Verified
laforge: Looks good to me, approved
fixeria: Looks good to me, approved
pespin: Looks good to me, but someone else must approve
diff --git a/scripts/docker-cleanup.sh b/scripts/docker-cleanup.sh
index fe134d2..0d19d7d 100755
--- a/scripts/docker-cleanup.sh
+++ b/scripts/docker-cleanup.sh
@@ -1,6 +1,40 @@
#!/bin/sh -x
# https://osmocom.org/projects/osmocom-servers/wiki/Docker_cache_clean_up
+kill_docker_containers_running_longer_than_24h() {
+ docker ps
+ set +x
+
+ local date_24h_ago="$(date "+%s" -d"24 hours ago")"
+ docker ps --format "{{.ID}}|{{.Names}}|{{.CreatedAt}}" | while read -r line; do
+ local id="$(echo "$line" | cut -d '|' -f 1)"
+ local name="$(echo "$line" | cut -d '|' -f 2)"
+ local created_at="$(echo "$line" | cut -d '|' -f 3 | cut -d ' ' -f 1-3)"
+ local date_created_at="$(date "+%s" -d "$created_at")"
+
+ if [ "$date_created_at" -gt "$date_24h_ago" ]; then
+ echo "$name: not running for >24h"
+ continue
+ fi
+
+ case "$name" in
+ jenkins-*|*ttcn3*) ;;
+ *)
+ echo "$name: does not match name pattern"
+ continue
+ ;;
+ esac
+
+ echo "$name ($id): has been running for >24h, killing"
+ docker kill "$id"
+ done
+
+ set -x
+ docker ps
+}
+
+kill_docker_containers_running_longer_than_24h
+
# delete all containers where we forgot to use --rm with docker run,
# older than 24 hours
docker container prune --filter "until=24h" -f
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/34645?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I58c17b57c998eaba411658e83b7295d7cfcf9a23
Gerrit-Change-Number: 34645
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
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-MessageType: merged
Attention is currently required from: jolly, pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/34626?usp=email )
Change subject: ASCI: Add System Information 10 support
......................................................................
Patch Set 2:
(6 comments)
Patchset:
PS2:
> I also don't like the timer. […]
SI10 is actually not needed for the call establishment, it's needed for quicker cell change. Without SI10 a phone participating a group call would need to first tune to BCCH of each neighbor to see if the current group call is also ongoing there or not -- this would cause a gap in the call.
IIUC, the payload of SI10 is expected to remain static as long as a) there are no neighbor list changes, b) no ongoing group calls being released, and c) no new group calls being established. Maybe we can trigger SI10 generation and sending if a), b), or c) happens?
File src/osmo-bsc/system_information.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/34626/comment/abfe25bf_b72c4afd
PS2, Line 1420: struct gsm_subscriber_connection *conn
should be `const`
https://gerrit.osmocom.org/c/osmo-bsc/+/34626/comment/b988a2f5_69d6cfbe
PS2, Line 1424: *n_bts, *l_bts
cosmetic: better declare these two separately, so they're not hidden behind the `s_bts` assignment. Wait, they're only used within the for-loop? Then they should be moved there.
https://gerrit.osmocom.org/c/osmo-bsc/+/34626/comment/7c9d144a_cda5d3da
PS2, Line 1428: unsigned int save_cur_bit;
: struct gsm_subscriber_connection *c;
both vars can be moved to the scope of use (for-loop)
https://gerrit.osmocom.org/c/osmo-bsc/+/34626/comment/7983ba8f_7fe8cfe7
PS2, Line 1447: 32
where this limit is coming from?
is there a macro? if not, at least add a comment?
https://gerrit.osmocom.org/c/osmo-bsc/+/34626/comment/668a1787_e10481d1
PS2, Line 1499: /* Do spare padding. We cannot do it earlier, because encoding might corrupt it if differenctial cell info
> the same "differential cell info" mentioned a few lines above I guess...
Indeed, SI10 employs so-called differential encoding: you encode all the info for the first BTS and then only those parameters that differ for the remaining BTSs.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/34626?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Icd3101e6dd935a57f003253aaef400c2cf95a0c3
Gerrit-Change-Number: 34626
Gerrit-PatchSet: 2
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 04 Oct 2023 19:06:51 +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/+/34645?usp=email )
Change subject: scripts/docker-cleanup: remove containers > 24h
......................................................................
scripts/docker-cleanup: remove containers > 24h
Remove containers starting with jenkins- or having ttcn3 in the name, if
they have been running for more than 24 hours. This can happen with the
ttcn3 testsuites, as they typically start multiple docker containers in
the background (one per Osmocom program) before they start the testsuite
docker container in the foreground. Usually the clean up trap makes sure
that all containers get killed, but we have seen that a few containers
have been running for a few months. One reason for this could be
temporary loss of connection between the jenkins server and the node
running the job.
Extend the clean script to remove the containers that were not properly
removed by the clean up trap.
Historically we used to kill docker containers of the same name before
starting a testsuite, but this had the downside that we could not start
the same testsuite multiple times in parallel. This was refactored in
docker-playground Ifcd384272c56d585e220e2588f2186dc110902ed.
Change-Id: I58c17b57c998eaba411658e83b7295d7cfcf9a23
---
M scripts/docker-cleanup.sh
1 file changed, 61 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/45/34645/1
diff --git a/scripts/docker-cleanup.sh b/scripts/docker-cleanup.sh
index fe134d2..0d19d7d 100755
--- a/scripts/docker-cleanup.sh
+++ b/scripts/docker-cleanup.sh
@@ -1,6 +1,40 @@
#!/bin/sh -x
# https://osmocom.org/projects/osmocom-servers/wiki/Docker_cache_clean_up
+kill_docker_containers_running_longer_than_24h() {
+ docker ps
+ set +x
+
+ local date_24h_ago="$(date "+%s" -d"24 hours ago")"
+ docker ps --format "{{.ID}}|{{.Names}}|{{.CreatedAt}}" | while read -r line; do
+ local id="$(echo "$line" | cut -d '|' -f 1)"
+ local name="$(echo "$line" | cut -d '|' -f 2)"
+ local created_at="$(echo "$line" | cut -d '|' -f 3 | cut -d ' ' -f 1-3)"
+ local date_created_at="$(date "+%s" -d "$created_at")"
+
+ if [ "$date_created_at" -gt "$date_24h_ago" ]; then
+ echo "$name: not running for >24h"
+ continue
+ fi
+
+ case "$name" in
+ jenkins-*|*ttcn3*) ;;
+ *)
+ echo "$name: does not match name pattern"
+ continue
+ ;;
+ esac
+
+ echo "$name ($id): has been running for >24h, killing"
+ docker kill "$id"
+ done
+
+ set -x
+ docker ps
+}
+
+kill_docker_containers_running_longer_than_24h
+
# delete all containers where we forgot to use --rm with docker run,
# older than 24 hours
docker container prune --filter "until=24h" -f
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/34645?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I58c17b57c998eaba411658e83b7295d7cfcf9a23
Gerrit-Change-Number: 34645
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: dexter, fixeria, fixeria, osmith.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/34575?usp=email )
Change subject: gprs_rlcmac_sched: check if we really use direct phy
......................................................................
Patch Set 3:
(1 comment)
File src/gprs_rlcmac_sched.cpp:
https://gerrit.osmocom.org/c/osmo-pcu/+/34575/comment/22488527_24303197
PS2, Line 491: if (bts->trx[trx].fl1h) {
> When we want to send the information which BTS model is used down to the PCU we might consider to us […]
I'd go for having a define in pcuif which doesn't need to necessarily be the same as present/used in osmo-bts or osmo-bsc. They could convert to it.
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/34575?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I0808950b1154bbb9a789c3f706ad9fb6618764ec
Gerrit-Change-Number: 34575
Gerrit-PatchSet: 3
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: fixeria <axilirator(a)gmail.com>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: fixeria <axilirator(a)gmail.com>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 04 Oct 2023 15:31:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: fixeria, fixeria, osmith, pespin.
dexter has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/34575?usp=email )
Change subject: gprs_rlcmac_sched: check if we really use direct phy
......................................................................
Patch Set 3:
(1 comment)
File src/gprs_rlcmac_sched.cpp:
https://gerrit.osmocom.org/c/osmo-pcu/+/34575/comment/8e461daa_8c11c6db
PS2, Line 491: if (bts->trx[trx].fl1h) {
> I think actually the first would be to decouple the feature "direct-phy" from "this bts doesn't supp […]
When we want to send the information which BTS model is used down to the PCU we might consider to use enum gsm_bts_type_variant:
https://gitea.osmocom.org/cellular-infrastructure/osmo-bts/src/branch/maste…
Unfortunately I am not entirely sure how to set this up. The enum is defined in bts.h. We may move it to pcuif_proto.h so that it becomes available to for all entities. Or we just define a new one, but this would be redundant. Any ideas to solve this in a more elegant way? Or is there even something in libosmocore? I couldn't find anything.
Even more unfotunately: its already a mess, osmo-bsc already has its own definition of that same enum:
https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc/src/branch/maste…
Maybe it could even have a healthy effect to define that enum in pcuif_proto.h so that we always can be sure that all entities have the same definition.
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/34575?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I0808950b1154bbb9a789c3f706ad9fb6618764ec
Gerrit-Change-Number: 34575
Gerrit-PatchSet: 3
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: fixeria <axilirator(a)gmail.com>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: fixeria <axilirator(a)gmail.com>
Gerrit-Comment-Date: Wed, 04 Oct 2023 15:25:45 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: comment
dexter has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/34585?usp=email )
Change subject: rename sysmo_direct_dsp to direct_phy
......................................................................
rename sysmo_direct_dsp to direct_phy
The name sysmo_direct_dsp is not entirely correct. It should be just
"sysmo" if we follow the rules that the "PCU_IF_FLAG_" prefix is
supposed to be chopped off here.
In pcuif_proto.h, we have renamed PCU_IF_FLAG_SYSMO to
PCU_IF_FLAG_DIRECT_PHY. (see Depends), so let's rename the flag here to
"direct_phy".
Related: OS#6191
Depends: osmo-pcu.git I29b7b78a3a91d062b9ea3cd72623d30618cd3f0b
Change-Id: Ib67c4441d0077822d0f9cbf29338fedeb916f287
---
M library/PCUIF_Types.ttcn
1 file changed, 22 insertions(+), 3 deletions(-)
Approvals:
fixeria: Looks good to me, approved
pespin: Looks good to me, but someone else must approve
Jenkins Builder: Verified
diff --git a/library/PCUIF_Types.ttcn b/library/PCUIF_Types.ttcn
index 6be45df..8fb0be3 100644
--- a/library/PCUIF_Types.ttcn
+++ b/library/PCUIF_Types.ttcn
@@ -60,7 +60,7 @@
type record PCUIF_Flags {
boolean bts_active,
- boolean sysmo_direct_dsp,
+ boolean direct_phy,
BIT14 spare,
boolean cs1,
boolean cs2,
@@ -819,7 +819,7 @@
const PCUIF_Flags c_PCUIF_Flags_default := {
bts_active := true,
- sysmo_direct_dsp := false,
+ direct_phy := false,
spare := '00000000000000'B,
cs1 := true,
cs2 := true,
@@ -839,7 +839,7 @@
const PCUIF_Flags c_PCUIF_Flags_noMCS := {
bts_active := true,
- sysmo_direct_dsp := false,
+ direct_phy := false,
spare := '00000000000000'B,
cs1 := true,
cs2 := true,
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/34585?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Ib67c4441d0077822d0f9cbf29338fedeb916f287
Gerrit-Change-Number: 34585
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: merged