osmith has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/38358?usp=email )
Change subject: jobs/build-kernels-testenv: add build-kernel-none
......................................................................
jobs/build-kernels-testenv: add build-kernel-none
Create a dummy output/linux file, that the jobs generated by
ttcn3-testsuites-testenv can copy (via copyartifact) when setting the
kernel to "none".
Without this, the ttcn3-testsuites-testenv.yml would need to become more
complex, as it is not possible in jenkins job builder templates to only
do the copyartifact block conditionally if kernel != "none".
Another solution would be using shell logic like the following:
if [ "$KERNEL" != "none" ]; then
wget -q -O .linux "https://jenkins.osmocom.org/..."
fi
But this has the disadvantage that jenkins is not aware of the file and
therefore we cannot track easily which linux kernel build was used in
the job. With the copyartifact method, we can click on "See
Fingerprints" and find which job built the kernel. Example:
https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-net-next/147…
Change-Id: I0b2367558a2b73c06267bc65f17cfcc224f35002
---
M jobs/build-kernels-testenv.yml
1 file changed, 24 insertions(+), 0 deletions(-)
Approvals:
laforge: Looks good to me, approved
Jenkins Builder: Verified
pespin: Looks good to me, but someone else must approve
diff --git a/jobs/build-kernels-testenv.yml b/jobs/build-kernels-testenv.yml
index 20dfc0f..cde1706 100644
--- a/jobs/build-kernels-testenv.yml
+++ b/jobs/build-kernels-testenv.yml
@@ -81,3 +81,27 @@
wrappers:
- ansicolor:
colormap: xterm
+
+- job:
+ name: 'build-kernel-none'
+ project-type: freestyle
+ defaults: global
+ description: |
+ Dummy job to allow specifying "none" as kernel in
+ <a href="https://gitea.osmocom.org/osmocom/osmo-ci/src/branch/master/jobs/ttcn3-test…">ttcn3-testsuites-testenv.yml</a>.
+ node: "osmocom-master"
+ builders:
+ - shell: |-
+ mkdir output
+ echo "dummy from build-kernel-none jenkins job" > output/linux
+ publishers:
+ - archive:
+ allow-empty: false
+ artifacts: output/**/*
+ case-sensitive: true
+ default-excludes: true
+ fingerprint: false
+ only-if-success: false
+ properties:
+ - build-discarder:
+ num-to-keep: 10
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/38358?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: I0b2367558a2b73c06267bc65f17cfcc224f35002
Gerrit-Change-Number: 38358
Gerrit-PatchSet: 2
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-Reviewer: pespin <pespin(a)sysmocom.de>
laforge has submitted this change. ( https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email )
Change subject: Remove sync() after writing VTY config
......................................................................
Remove sync() after writing VTY config
Running sync() after writing VTY config causes the process to stop for
a fraction of a second. This may result in delayed processing that
causes buffer underruns, overflows and delay. This is a problem with
applications that do real-time signal processing such as osmo-trx and
osmo-bts.
After some discussions, I decided to simply remove the sync() commands
from the VTY's write function. There is still a backup file created
of the previously saved configuration before writing the current
configurtion. Loosing current configuration caused by a system crash
afterwards is very unlikely with modern file systems.
Related: OS#6438
Change-Id: I3cb2ee68b2e4c730f96522208c4abf00d0f49a44
---
M src/vty/command.c
1 file changed, 0 insertions(+), 2 deletions(-)
Approvals:
laforge: Looks good to me, approved
Jenkins Builder: Verified
diff --git a/src/vty/command.c b/src/vty/command.c
index 1719690..8f87e7d 100644
--- a/src/vty/command.c
+++ b/src/vty/command.c
@@ -3451,7 +3451,6 @@
unlink(config_file_tmp);
return -3;
}
- sync();
if (unlink(config_file) != 0) {
*outpath = talloc_strdup(tall_vty_cmd_ctx, config_file);
talloc_free(config_file_sav);
@@ -3468,7 +3467,6 @@
return -5;
}
unlink(config_file_tmp);
- sync();
talloc_free(config_file_sav);
talloc_free(config_file_tmp);
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: merged
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3cb2ee68b2e4c730f96522208c4abf00d0f49a44
Gerrit-Change-Number: 37798
Gerrit-PatchSet: 7
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: Hoernchen <ewild(a)sysmocom.de>
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: laforge, pespin.
jolly has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email )
Change subject: Remove sync() after writing VTY config
......................................................................
Patch Set 7:
(2 comments)
Patchset:
PS5:
> I just saw this paper of using sync() as a covert channel between two programs on the same host. […]
Done
PS5:
> I'm fine with removing it.
Done
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/37798?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: I3cb2ee68b2e4c730f96522208c4abf00d0f49a44
Gerrit-Change-Number: 37798
Gerrit-PatchSet: 7
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: Hoernchen <ewild(a)sysmocom.de>
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 08 Oct 2024 12:06:41 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: jolly <andreas(a)eversberg.eu>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>