BRANCH_CImasterosmo-ci.git branch BRANCH_CIStringParameterDefinitionCOMMENT_TYPEset by gerrit verification pipeline jobCOMMENT_TYPEStringParameterDefinitionDISTROset by gerrit verification pipeline jobDISTROStringParameterDefinitionGERRIT_BRANCHset by gerrit verification pipeline jobGERRIT_BRANCHStringParameterDefinitionGERRIT_CHANGE_NUMBERset by gerrit verification pipeline jobGERRIT_CHANGE_NUMBERStringParameterDefinitionGERRIT_HOSTset by gerrit verification pipeline jobGERRIT_HOSTStringParameterDefinitionGERRIT_PATCHSET_NUMBERset by gerrit verification pipeline jobGERRIT_PATCHSET_NUMBERStringParameterDefinitionGERRIT_PATCHSET_REVISIONset by gerrit verification pipeline jobGERRIT_PATCHSET_REVISIONStringParameterDefinitionGERRIT_PATCHSET_UPLOADER_NAMEset by gerrit verification pipeline jobGERRIT_PATCHSET_UPLOADER_NAMEStringParameterDefinitionGERRIT_PORTset by gerrit verification pipeline jobGERRIT_PORTStringParameterDefinitionGERRIT_PROJECTset by gerrit verification pipeline jobGERRIT_PROJECTStringParameterDefinitionGERRIT_REFSPECset by gerrit verification pipeline jobGERRIT_REFSPECStringParameterDefinitionGERRIT_REPO_URLset by gerrit verification pipeline jobGERRIT_REPO_URLStringParameterDefinitionPIPELINE_BUILD_URLset by gerrit verification pipeline jobPIPELINE_BUILD_URLStringParameterDefinitionPROJECT_NAMEset by gerrit verification pipeline jobPROJECT_NAMEStringParameterDefinitionhttps://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/Build job of CI for patches sent to <a href="https://gerrit.osmocom.org/#/q/status:open+project:osmo-hlr">osmo-hlr</a> <br/><br/> <b>Auto-generated using Jenkins Job Builder. DO NOT EDIT MANUALLY!</b> <!-- Managed by Jenkins Job Builder -->gerrit-osmo-hlr-buildgerrit-osmo-hlr-buildgerrit-osmo-hlr-buildgerrit-osmo-hlr-buildhttps://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/trueStarted by upstream project "gerrit-osmo-hlr" build number 152152gerrit-osmo-hlrjob/gerrit-osmo-hlr/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42018GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION459ae06783dadfd67130dd9fa61568eef6d4146fGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTosmo-hlrGERRIT_REFSPECrefs/changes/18/42018/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-hlr/152/PROJECT_NAMEosmo-hlrBRANCH_CImaster000089526895261.0051835183144addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.1addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.156a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.2a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.23481335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.181335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.13142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.1152459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrfalse#1528952689526gerrit-osmo-hlr-build #152152falsefalse15222642SUCCESS1770114833655https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/152/src/hlr.c459ae06783dadfd67130dd9fa61568eef6d4146f1770113355000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deosmo-hlr: Force log stderr blocking-io in --db-check mode When --db-check is used, osmo-hlr actually becomes a synchronous non-interactive program instead of a daemon. In that case, we want to use blocking-io since it doesn't use the event loop, so we want to flush all logging synchronously before exiting. Usually the user will pass the same osmo-hlr.cfg when running with --db-check, which means most probably won't be using blocking-io (as expected when osmo-hlr runs in daemon mode). Since --db-check converts osmo-hlr to a cmdline which exits after checks are done, we actually want to force blocking-io in that case, so that all content is written to stderr before finishing the process. Change-Id: If5e505383086cc55d724c0d6891756c8d94fa267 2026-02-03 11:09:15 +0100459ae06783dadfd67130dd9fa61568eef6d4146fosmo-hlr: Force log stderr blocking-io in --db-check modeeditsrc/hlr.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/blueStarted by upstream project "gerrit-osmo-hlr" build number 152152gerrit-osmo-hlrjob/gerrit-osmo-hlr/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42018GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION459ae06783dadfd67130dd9fa61568eef6d4146fGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTosmo-hlrGERRIT_REFSPECrefs/changes/18/42018/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-hlr/152/PROJECT_NAMEosmo-hlrBRANCH_CImaster000089526895261.0051835183144addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.1addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.156a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.2a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.23481335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.181335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.13142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.1152459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrfalse#1528952689526gerrit-osmo-hlr-build #152152falsefalse15222642SUCCESS1770114833655https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/152/src/hlr.c459ae06783dadfd67130dd9fa61568eef6d4146f1770113355000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deosmo-hlr: Force log stderr blocking-io in --db-check mode When --db-check is used, osmo-hlr actually becomes a synchronous non-interactive program instead of a daemon. In that case, we want to use blocking-io since it doesn't use the event loop, so we want to flush all logging synchronously before exiting. Usually the user will pass the same osmo-hlr.cfg when running with --db-check, which means most probably won't be using blocking-io (as expected when osmo-hlr runs in daemon mode). Since --db-check converts osmo-hlr to a cmdline which exits after checks are done, we actually want to force blocking-io in that case, so that all content is written to stderr before finishing the process. Change-Id: If5e505383086cc55d724c0d6891756c8d94fa267 2026-02-03 11:09:15 +0100459ae06783dadfd67130dd9fa61568eef6d4146fosmo-hlr: Force log stderr blocking-io in --db-check modeeditsrc/hlr.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/Build stability: No recent builds failed.icon-health-80plushealth-80plus.png100falsefalseStarted by upstream project "gerrit-osmo-hlr" build number 152152gerrit-osmo-hlrjob/gerrit-osmo-hlr/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42018GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION459ae06783dadfd67130dd9fa61568eef6d4146fGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTosmo-hlrGERRIT_REFSPECrefs/changes/18/42018/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-hlr/152/PROJECT_NAMEosmo-hlrBRANCH_CImaster000089526895261.0051835183144addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.1addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.156a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.2a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.23481335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.181335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.13142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.1152459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrfalse#1528952689526gerrit-osmo-hlr-build #152152falsefalse15222642SUCCESS1770114833655https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/152/src/hlr.c459ae06783dadfd67130dd9fa61568eef6d4146f1770113355000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deosmo-hlr: Force log stderr blocking-io in --db-check mode When --db-check is used, osmo-hlr actually becomes a synchronous non-interactive program instead of a daemon. In that case, we want to use blocking-io since it doesn't use the event loop, so we want to flush all logging synchronously before exiting. Usually the user will pass the same osmo-hlr.cfg when running with --db-check, which means most probably won't be using blocking-io (as expected when osmo-hlr runs in daemon mode). Since --db-check converts osmo-hlr to a cmdline which exits after checks are done, we actually want to force blocking-io in that case, so that all content is written to stderr before finishing the process. Change-Id: If5e505383086cc55d724c0d6891756c8d94fa267 2026-02-03 11:09:15 +0100459ae06783dadfd67130dd9fa61568eef6d4146fosmo-hlr: Force log stderr blocking-io in --db-check modeeditsrc/hlr.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/Started by upstream project "gerrit-osmo-hlr" build number 152152gerrit-osmo-hlrjob/gerrit-osmo-hlr/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42018GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION459ae06783dadfd67130dd9fa61568eef6d4146fGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTosmo-hlrGERRIT_REFSPECrefs/changes/18/42018/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-hlr/152/PROJECT_NAMEosmo-hlrBRANCH_CImaster000089526895261.0051835183144addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.1addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.156a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.2a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.23481335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.181335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.13142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.1152459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrfalse#1528952689526gerrit-osmo-hlr-build #152152falsefalse15222642SUCCESS1770114833655https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/152/src/hlr.c459ae06783dadfd67130dd9fa61568eef6d4146f1770113355000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deosmo-hlr: Force log stderr blocking-io in --db-check mode When --db-check is used, osmo-hlr actually becomes a synchronous non-interactive program instead of a daemon. In that case, we want to use blocking-io since it doesn't use the event loop, so we want to flush all logging synchronously before exiting. Usually the user will pass the same osmo-hlr.cfg when running with --db-check, which means most probably won't be using blocking-io (as expected when osmo-hlr runs in daemon mode). Since --db-check converts osmo-hlr to a cmdline which exits after checks are done, we actually want to force blocking-io in that case, so that all content is written to stderr before finishing the process. Change-Id: If5e505383086cc55d724c0d6891756c8d94fa267 2026-02-03 11:09:15 +0100459ae06783dadfd67130dd9fa61568eef6d4146fosmo-hlr: Force log stderr blocking-io in --db-check modeeditsrc/hlr.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/Started by upstream project "gerrit-osmo-hlr" build number 152152gerrit-osmo-hlrjob/gerrit-osmo-hlr/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42018GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION459ae06783dadfd67130dd9fa61568eef6d4146fGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTosmo-hlrGERRIT_REFSPECrefs/changes/18/42018/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-hlr/152/PROJECT_NAMEosmo-hlrBRANCH_CImaster000089526895261.0051835183144addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.1addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.156a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.2a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.23481335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.181335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.13142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.1152459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrfalse#1528952689526gerrit-osmo-hlr-build #152152falsefalse15222642SUCCESS1770114833655https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/152/src/hlr.c459ae06783dadfd67130dd9fa61568eef6d4146f1770113355000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deosmo-hlr: Force log stderr blocking-io in --db-check mode When --db-check is used, osmo-hlr actually becomes a synchronous non-interactive program instead of a daemon. In that case, we want to use blocking-io since it doesn't use the event loop, so we want to flush all logging synchronously before exiting. Usually the user will pass the same osmo-hlr.cfg when running with --db-check, which means most probably won't be using blocking-io (as expected when osmo-hlr runs in daemon mode). Since --db-check converts osmo-hlr to a cmdline which exits after checks are done, we actually want to force blocking-io in that case, so that all content is written to stderr before finishing the process. Change-Id: If5e505383086cc55d724c0d6891756c8d94fa267 2026-02-03 11:09:15 +0100459ae06783dadfd67130dd9fa61568eef6d4146fosmo-hlr: Force log stderr blocking-io in --db-check modeeditsrc/hlr.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/Started by upstream project "gerrit-osmo-hlr" build number 152152gerrit-osmo-hlrjob/gerrit-osmo-hlr/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42018GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION459ae06783dadfd67130dd9fa61568eef6d4146fGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTosmo-hlrGERRIT_REFSPECrefs/changes/18/42018/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-hlr/152/PROJECT_NAMEosmo-hlrBRANCH_CImaster000089526895261.0051835183144addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.1addc0dc1fd76c9868a774d2532faa2995eafff31addc0dc1fd76c9868a774d2532faa2995eafff31osmith/1.9.156a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.2a6e983b98550adda992d821f8c0daf92e63ddc1ea6e983b98550adda992d821f8c0daf92e63ddc1eosmith/1.6.23481335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.181335271b9f8c74cbafceeb11ccede5074bc93cc81335271b9f8c74cbafceeb11ccede5074bc93ccosmith/1.5.13142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.142f82975f23b381a2fcfb42aacbd72660a0ee7f442f82975f23b381a2fcfb42aacbd72660a0ee7f4osmith/1.6.1152459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmaster459ae06783dadfd67130dd9fa61568eef6d4146f459ae06783dadfd67130dd9fa61568eef6d4146fmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-hlrfalse#1528952689526gerrit-osmo-hlr-build #152152falsefalse15222642SUCCESS1770114833655https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/152/src/hlr.c459ae06783dadfd67130dd9fa61568eef6d4146f1770113355000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deosmo-hlr: Force log stderr blocking-io in --db-check mode When --db-check is used, osmo-hlr actually becomes a synchronous non-interactive program instead of a daemon. In that case, we want to use blocking-io since it doesn't use the event loop, so we want to flush all logging synchronously before exiting. Usually the user will pass the same osmo-hlr.cfg when running with --db-check, which means most probably won't be using blocking-io (as expected when osmo-hlr runs in daemon mode). Since --db-check converts osmo-hlr to a cmdline which exits after checks are done, we actually want to force blocking-io in that case, so that all content is written to stderr before finishing the process. Change-Id: If5e505383086cc55d724c0d6891756c8d94fa267 2026-02-03 11:09:15 +0100459ae06783dadfd67130dd9fa61568eef6d4146fosmo-hlr: Force log stderr blocking-io in --db-check modeeditsrc/hlr.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/153BRANCH_CImasterosmo-ci.git branch BRANCH_CIStringParameterDefinitionCOMMENT_TYPEset by gerrit verification pipeline jobCOMMENT_TYPEStringParameterDefinitionDISTROset by gerrit verification pipeline jobDISTROStringParameterDefinitionGERRIT_BRANCHset by gerrit verification pipeline jobGERRIT_BRANCHStringParameterDefinitionGERRIT_CHANGE_NUMBERset by gerrit verification pipeline jobGERRIT_CHANGE_NUMBERStringParameterDefinitionGERRIT_HOSTset by gerrit verification pipeline jobGERRIT_HOSTStringParameterDefinitionGERRIT_PATCHSET_NUMBERset by gerrit verification pipeline jobGERRIT_PATCHSET_NUMBERStringParameterDefinitionGERRIT_PATCHSET_REVISIONset by gerrit verification pipeline jobGERRIT_PATCHSET_REVISIONStringParameterDefinitionGERRIT_PATCHSET_UPLOADER_NAMEset by gerrit verification pipeline jobGERRIT_PATCHSET_UPLOADER_NAMEStringParameterDefinitionGERRIT_PORTset by gerrit verification pipeline jobGERRIT_PORTStringParameterDefinitionGERRIT_PROJECTset by gerrit verification pipeline jobGERRIT_PROJECTStringParameterDefinitionGERRIT_REFSPECset by gerrit verification pipeline jobGERRIT_REFSPECStringParameterDefinitionGERRIT_REPO_URLset by gerrit verification pipeline jobGERRIT_REPO_URLStringParameterDefinitionPIPELINE_BUILD_URLset by gerrit verification pipeline jobPIPELINE_BUILD_URLStringParameterDefinitionPROJECT_NAMEset by gerrit verification pipeline jobPROJECT_NAMEStringParameterDefinitiontruefalsehudson.plugins.git.GitSCM--ffdefaulta1=default,a2=default,a3=default,a4=default,osmocom-gerritgerrit-osmo-hlr-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerritgerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrita1=default,a2=default,a3=default,a4=default,label=osmocom-gerrithttps://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/true152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/blue152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/Build stability: No recent builds failed.icon-health-80plushealth-80plus.png100falsefalse152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/152https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-osmo-hlr-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/152/153truefalse