Bug #5619
closedosmocom OBS nightly job fails since 2 nights ago
100%
Description
lsat few lines are:
+ mv /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmo-dsp.spec.new /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmo-dsp.spec ++ grep '^Version: ' /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmodsp_0.4.0.5.6bf7.202207170052.dsc ++ cut -d: -f2- ++ xargs + version=0.4.0.5.6bf7.202207170052 + case $version in + '[' -n '' ']' + sed -i 's/^Version:.*/Version: 0.4.0.5.6bf7.202207170052/g' /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmo-dsp.spec ++ cd /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp ++ ls -1 'libosmo-dsp_*.tar.*' ls: cannot access 'libosmo-dsp_*.tar.*': No such file or directory + tarball= Build step 'Execute shell' marked build as failure Sending e-mails to: jenkins-notifications@lists.osmocom.org Finished: FAILURE
Didn't look at it in more detail, but could it be that the build job makes the blind assumption that an earlier tar.gz from the last night exists, but libosmo-dsp has none?
This might be the root cause of #5618
In general, I think it is somewhat sub-optimal of the OBS job (nightly/latest) has an error for one specific package, it shouldn't stop processing for all the other packages. can't we somehow trap/catch the error, memorize it and continue with the other packages, and then at the final exit report the non-success exit code so jenkins shows the job as failed but still have only one package affected by a problem?
Related issues
Updated by laforge almost 2 years ago
- Related to Bug #5618: obs-nightly: centos8 fails to build / OBS nightly builds git from 2 days earlier added
Updated by osmith almost 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Fixed in:
https://gerrit.osmocom.org/c/osmo-ci/+/28637
I've merged it directly given that this is urgent and the fix is trivial, and I tested it. Triggered the jenkins job to build packages.
In general, I think it is somewhat sub-optimal of the OBS job (nightly/latest) has an error for one specific package, it shouldn't stop processing for all the other packages.
Agreed!
can't we somehow trap/catch the error, memorize it and continue with the other packages, and then at the final exit report the non-success exit code so jenkins shows the job as failed but still have only one package affected by a problem?
Yes, I'll change the scripts to do this.