Re: CI Pipelines
Gilles Caulier <[email protected]> Sun, 18 Sep 2022 17:09:50 +0200
| Newsgroups | gmane.comp.kde.digikam.devel |
|---|---|
| Message-ID | <CAHFG6sG9qs7U9XMY6MPmtNRWhjs=BpRr5o5p7LcSCK4sgvvMyA@mail.gmail.com> |
Few days ago, I saw an ASAN warning at the run time of a unit test about IM wrong memory usage. It sounds like it disappears now... Too many people from the KDE team touch the CI in gitlab... The error about 1 hour time-out is due to gitlab limitation. If you want to run CI/CD for more than 1 hour... you need to pay (:-)))... Gilles Le dim. 18 sept. 2022 à 15:31, Steven Robbins <[email protected]> a écrit : > > On Saturday, September 17, 2022 11:33:06 P.M. CDT Gilles Caulier wrote: > > Hi, > > > > As i can see the dysfunction come from ImageMagick backend called by > > DMetadata parser. > > > > Typically, we have more than one metadata parser as Exiv2, ffmpeg, > > libraw, ExifTool, and Imagegic. > > This last one is less robust than the previous one, and depending of > > IM version installed on the CI computer, it can crash at run time. > > Are you saying that the version of ImageMagick on the CI builder has changed a > week ago? And that the failing code is within the ImageMagick library itself? > > The passing CI run claims it did NOT find Image Magick (but did find the image > magic version??): > > -- Could NOT find ImageMagick (missing: ImageMagick_Magick++_LIBRARY) (found > version "7.1.0-47") > -- ImageMagick_FOUND: FALSE > -- ImageMagick_VERSION_STRING: 7.1.0-47 > -- ImageMagick_EXECUTABLE_DIR: /usr/bin > -- ImageMagick_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_LIBRARIES: /usr/lib64/ > libMagickCore-7.Q16HDRI.so;/usr/lib64/libMagickWand-7.Q16HDRI.so > -- ImageMagick_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > -- ImageMagick_Magick++_INCLUDE_DIRS: > -- ImageMagick_Magick++_LIBRARY: ImageMagick_Magick++_LIBRARY-NOTFOUND > -- ImageMagick_Magick++_DEFINITIONS: > -- ImageMagick_MagickCore_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_MagickCore_LIBRARY: /usr/lib64/ > libMagickCore-7.Q16HDRI.so > -- ImageMagick_MagickCore_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > -- ImageMagick_MagickWand_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_MagickWand_LIBRARY: /usr/lib64/ > libMagickWand-7.Q16HDRI.so > -- ImageMagick_MagickWand_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > > > Today ImageMagick *IS* found (with same version): > > -- Found ImageMagick: /usr/lib64/libMagick++-7.Q16HDRI.so (found version > "7.1.0-47") > -- ImageMagick_FOUND: TRUE > -- ImageMagick_VERSION_STRING: 7.1.0-47 > -- ImageMagick_EXECUTABLE_DIR: /usr/bin > -- ImageMagick_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_LIBRARIES: /usr/lib64/libMagick+ > +-7.Q16HDRI.so;/usr/lib64/libMagickCore-7.Q16HDRI.so;/usr/lib64/ > libMagickWand-7.Q16HDRI.so > -- ImageMagick_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > -- ImageMagick_Magick++_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_Magick++_LIBRARY: /usr/lib64/libMagick++-7.Q16HDRI.so > -- ImageMagick_Magick++_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > -- ImageMagick_MagickCore_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_MagickCore_LIBRARY: /usr/lib64/ > libMagickCore-7.Q16HDRI.so > -- ImageMagick_MagickCore_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > -- ImageMagick_MagickWand_INCLUDE_DIRS: /usr/include/ImageMagick-7 > -- ImageMagick_MagickWand_LIBRARY: /usr/lib64/ > libMagickWand-7.Q16HDRI.so > -- ImageMagick_MagickWand_DEFINITIONS: -DMAGICKCORE_HDRI_ENABLE=1;- > DMAGICKCORE_QUANTUM_DEPTH=16 > > > Maybe that's the difference? > > Weirdly, the most recent CI run [1] has just one failure -- and this time due > to a timeout. No bad memory access -- was it addressed? > > [1] https://invent.kde.org/graphics/digikam/-/jobs/483635/raw > > -Steve >