Tellico failing CI with exiv2 error
Hi all, Can anyone help with a failing CI test for Tellico? It just started recently, and looks to be due to kfilemetadata not finding the libexiv2 library. I'm not sure what might have changed. Nothing in recent Tellico commits seems to be related. >From https://invent.kde.org/office/tellico/-/jobs/1042785/raw: QDEBUG : FileListingTest::testXMPData() kf.filemetadata: Found plugin with metadata: "/builds/office/tellico/_install/lib64/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so" QWARN : FileListingTest::testXMPData() kf.filemetadata: Could not create Extractor: "/builds/office/tellico/_install/lib64/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so" QWARN : FileListingTest::testXMPData() kf.filemetadata: "Cannot load library /builds/office/tellico/_install/lib64/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so: (libexiv2.so.27: cannot open shared object file: No such file or directory)" Since Tellico's test looks as exiv data is read by Tellico, it obviously fails. I believe I've isolated the cause, but I guess it could be something else, but the error about not loading the library seems rather relevant. https://invent.kde.org/office/tellico/-/jobs/1040551 was the first failure yesterday. Thanks for any help, Robby
Re: Tellico failing CI with exiv2 error
On Donnerstag, 6. Juli 2023 17:43:11 CEST Robby Stephenson wrote: > Hi all, > > Can anyone help with a failing CI test for Tellico? It just started > recently, and looks to be due to kfilemetadata not finding the libexiv2 > library. I'm not sure what might have changed. Nothing in recent Tellico > commits seems to be related. Broken CI setup. KFiletaData was apparently built against libexiv2 0.27, which cannot be found on the CI host. Probably libexiv2 on the CI host was updated to libexiv2 0.28, but KFileMetaData was not rebuilt. Automatic dependency tracking for artifacts from the CI system is obviously incomplete (or likely nonexistent). Regards, Stefan > From https://invent.kde.org/office/tellico/-/jobs/1042785/raw: > ... > QWARN : FileListingTest::testXMPData() > kf.filemetadata: "Cannot load library > /builds/office/tellico/_install/lib64/plugins/kf5/kfilemetadata/kfilemetada > ta_exiv2extractor.so: (libexiv2.so.27: cannot open shared object file: No > such file or directory)" signature.asc Description: This is a digitally signed message part.
Re: Tellico failing CI with exiv2 error
> Probably libexiv2 on the CI host was updated to libexiv2 0.28, but > KFileMetaData was not rebuilt. Automatic dependency tracking for artifacts > from the CI system is obviously incomplete (or likely nonexistent). Isn’t that (among other things) the reason kexiv2 exists? Cheers Kai Uwe
Re: Tellico failing CI with exiv2 error
Am Donnerstag, 6. Juli 2023, 18:43:50 CEST schrieb Kai Uwe Broulik: > > Probably libexiv2 on the CI host was updated to libexiv2 0.28, but > > KFileMetaData was not rebuilt. Automatic dependency tracking for > > artifacts > > > from the CI system is obviously incomplete (or likely nonexistent). > > Isn’t that (among other things) the reason kexiv2 exists? Does not help if kexiv2 is not rebuilt and deployed as artifact when exiv2 on the image changed in a incompatible version? Triggered the needed manual rerun of kfilemetadata now, so the exiv plugin artifact is updated to the match the current base image. Also reran the tellico jump afterwards, seems to pass now again. Curious: are the images regenerated automatically or manually? in both cases, triggering also seed runs should be something part of that process? As we seem to run into such things again and again? Cheers Friedrich
