Closed dcesari closed 4 years ago
Possibly useful information: the latest prebuilt smnd binary package, using wreport version 3.20 does not show the problem.
A rebuild of bufr2netcdf against new wreport was enough to cure the problem. How can we detect these problems? Bufr2netcdf is not automatically tested at wreport updates and it's not the first time it fails runtime after updating wreport.
Would it be possible to add to the CI a rebuild+test of bufr2netcdf and dballe after wreport tests pass?
The rebuild should be triggered after a new packaged version of wreport or after a commit in the master branch of wreport?
after a new packaged version is enough
Il giorno lun 29 lug 2019 alle ore 14:41 Emanuele Di Giacomo < notifications@github.com> ha scritto:
The rebuild should be triggered after a new packaged version of wreport or after a commit in the master branch of wreport?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ARPA-SIMC/wreport/issues/29?email_source=notifications&email_token=AAFGLJS7IBWO6PZYGYTEA6LQB3QORA5CNFSM4H44BRQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ASKOI#issuecomment-515974457, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFGLJXX5Q7UBHJDLCBUH63QB3QORANCNFSM4H44BRQA .
It seems that Copr doesn't allow to fire a custom event (e.g. a Travis build), but we could schedule a daily build from Travis.
@dcesari @brancomat @pat1 what do you think about a daily Travis rebuild of all our packages? This would solve the problem of automatically testing a software against the latest version of its dependencies.
A daily rebuild is probably overshoot, wreport does not change often, I scheduled a monthly rebuild of bufr2netcdf, https://travis-ci.org/ARPA-SIMC/bufr2netcdf/settings do we need to extend to other packages?
with libwreport 3.21 and bufr2netcdf 1.5 (Fedora 28 and Centos):
with libwreport 3.18 and same bufr2netcdf (on Fedora24) it works.
I attach the bufr, but I think it does not depend on the message.
obs_1.zip