On Sat, 21 Mar 2026, Michael Niedermayer via ffmpeg-devel wrote:
Fifth,
the libcheckasm work was done by FFlabs people and discussed in FFlabs
meetings.
So unless I misunderstand the situation, we seem to have funded work that
now removes FFmpeg attribution or identity,
adds a dependency on external infrastructure, and moves testing in a
direction tied to systems FFmpeg does not control and previously did not choose.
Also just to clarify. this doesn't "move testing" at all.
Right now, ffmpeg has no selftests that the checkasm core logic works as
expected - it has checkasm tests that tests that the ffmpeg assembly works
as expected.
After merging a code drop of this, ffmpeg's testing would remain the same
(except that checkasm now is better at a number of things).
The code drop may or may not contain the new selftest files, depending on
whether people want the integration to include them or not. In the
proposed integration into the ffmpeg build system, the checkasm selftests
aren't built - but they could esasily be added if someone thinks it's
relevant.
Whether anything of that is tied into any specific CI system is entirely
orthogonal? The standalone repo has setup for running these selftests on a
bunch of runners. If you want the _new_ checkasm selftests executed as
part of e.g. make fate, that could be done. And then it would be executed
by the regular ffmpeg CI configurations we have now.
// Martin
_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
