Re: Hooked up the test data! -- DONE!!!

Steven Robbins <[email protected]> Wed, 05 Oct 2022 19:26:16 -0500

Newsgroups	gmane.comp.kde.digikam.devel
Message-ID	<4746641.GXAFRqVoOG@riemann>

Hello,

I'm happy to report that the last few kinks with digikam-test-data have been 
ironed out.   I have small video test files in a forked repo [1] which are 
being consumed by tests in a forked repo of digikam itself [2].

Before I start with merge requests, please have a quick look at [1] and let me 
know if you're OK with the file layout and naming.  There's only four test files 
at the moment so there's not a well-developed naming convention -- mostly it 
consists of using a sub-directory named "video"; I expect that later there 
will be one named "images".   

On Monday, October 3, 2022 9:18:21 A.M. CDT Steven Robbins wrote:

> So now my problem is the actual tests.  They run fine on my system -- I have
> tested both ffmpeg 4 and 5 -- but fail on all three testers.  The failure
> is right in the beginning -- at the load() call.  I had been supposing it
> was because the codec wasn't supported, but I changed codecslist.cpp to
> always print and the codec used in the file is listed.  So I'm boggled.

It turned out to be two distinct issues.

1. Windows had git-lfs installed but suse and freebsd did not.  This resulted 
in the latter two not actually having the file content available.  Ben has 
installed git-lfs for suse and put out a request to someone else for freebsd.

2. The Suse CI executer has a very very limited selection of codecs; so it was 
failing for this reason.  I finally worked out which codecs were available and 
transcoded the test file to mpeg2 to get the test to run.

-Steve

[1] https://invent.kde.org/srobbins/digikam-test-data
[2] https://invent.kde.org/srobbins/digikam

signature.asc (application/pgp-signature, 833 B)