From: Nicolas George <george@nsup.org> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] Test coverage for libavfilter negotiation Date: Wed, 4 Jun 2025 09:24:23 +0200 Message-ID: <aD_0p7RZLSd2iR_T@phare.normalesup.org> (raw) Hi. As I explained earlier in the “Subtitle Filtering Ramp-Up” thread: Any non-trivial progress on libavfilter requires touching the format negotiation code. The format negotiation code is very fragile and has almost no test coverage at all. Touching it as is would be suicidal. Therefore, any non-trivial progress on libavfilter requires first adding test coverage on the negotiation process. I started a long time ago: https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-August/299593.html but it is extremely boring work, I got bored and I could not take some air working on AVWriter. I do not intend to do boring things unless I can have some freedom doing fun things too. It is boring, but it is not very hard. Which is why I think it would be a good candidate to throw money at, if we have money that we can throw at needs. It could take the form of bounties: one line of coverage ⇒ one amount of money. It could work because there is an objective criterion: the test must pass as is but fail if we artificially remove or alter the line of code it covers. I can advise on the technical matter, I can review patches, list parts of the code that require coverage and explain what they do. But I do not know how do do the money part. Regards, -- Nicolas George _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2025-06-04 7:24 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-04 7:24 Nicolas George [this message] 2025-06-04 13:36 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=aD_0p7RZLSd2iR_T@phare.normalesup.org \ --to=george@nsup.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git