Actions
Bug #5619
closedosmocom OBS nightly job fails since 2 nights ago
Start date:
07/17/2022
Due date:
% Done:
100%
Spec Reference:
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
Actions