From: Kacper Michajlow <kasper93-at-gmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: softworkz <softworkz@hotmail.com> Subject: Re: [FFmpeg-devel] [PATCH 0/3] tests/fate: Improvements for running FATE on Windows/MSYS2 Date: Tue, 17 Jun 2025 00:43:35 +0200 Message-ID: <CABPLASQiM+hf=yJKeaUtuOWkFmLnh5o8oszVYwoCVsDh8-A0Kg@mail.gmail.com> (raw) In-Reply-To: <pull.77.ffstaging.FFmpeg.1747043987.ffmpegagent@gmail.com> On Mon, 12 May 2025 at 12:00, ffmpegagent <ffmpegagent@gmail.com> wrote: > > When setting up the new Patchword builders I noticed some issues when > running FATE tests on Windows. Initially I had them suppressed on the > builders, but this patchset should finally fix it. > > softworkz (3): > tests/fate: Fix subtitle fate tests on Windows > tests/source-check: Fix make inclusion-guard check EOL-agnostic I think ffmpeg repositories should always be checked out with LF line endings, there is nothing that expects those sources to have CRLF. If you like you can set attributes to all files to LF (not only subs), but essentially this should already be done by the user when checking the repository. (autocrlf should be considered harmful, the was bad idea to make git tooling smarter for its own good) > tests/hevc: Fix concat input when running in MSYS2 shell This is more tricky, but frankly, I don't like injecting platform specific workarounds into makefile files like that. Either maintain it yourself or do it in a more generic way, not just in one hevc test, because what if someone else adds a concat test? Do you expect them to know that some MSYS2 specific handling is needed? It shouldn't be. Also if you like to fix "fate paths", it should be done fully. Currently only relative paths are working, because some tests are doing things like "$(input)[bla]" which also trips patch conversion, so full unix path doesn't work, because it won't get converted to Windows one, Windows path doesn't work, because it would be mangled because of not escaped `\`. - Kacper _______________________________________________ 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 prev parent reply other threads:[~2025-06-16 22:43 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-05-12 9:59 ffmpegagent 2025-05-12 9:59 ` [FFmpeg-devel] [PATCH 1/3] tests/fate: Fix subtitle fate tests on Windows softworkz 2025-05-12 9:59 ` [FFmpeg-devel] [PATCH 2/3] tests/source-check: Fix make inclusion-guard check EOL-agnostic softworkz 2025-05-12 9:59 ` [FFmpeg-devel] [PATCH 3/3] tests/hevc: Fix concat input when running in MSYS2 shell softworkz 2025-05-12 16:53 ` Zhao Zhili 2025-05-12 17:04 ` softworkz . 2025-05-12 17:24 ` Zhao Zhili 2025-05-12 17:52 ` softworkz . 2025-05-13 14:23 ` [FFmpeg-devel] [PATCH v2 0/3] tests/fate: Improvements for running FATE on Windows/MSYS2 ffmpegagent 2025-05-13 14:23 ` [FFmpeg-devel] [PATCH v2 1/3] tests/fate: Fix subtitle fate tests on Windows softworkz 2025-05-13 14:23 ` [FFmpeg-devel] [PATCH v2 2/3] tests/source-check: Fix make inclusion-guard check EOL-agnostic softworkz 2025-05-22 10:41 ` Andreas Rheinhardt 2025-05-22 11:12 ` softworkz . 2025-05-22 11:20 ` softworkz . 2025-05-13 14:23 ` [FFmpeg-devel] [PATCH v2 3/3] tests/hevc: Fix concat input when running in MSYS2 shell softworkz 2025-05-22 2:55 ` [FFmpeg-devel] [PATCH v2 0/3] tests/fate: Improvements for running FATE on Windows/MSYS2 softworkz . 2025-06-16 22:43 ` Kacper Michajlow [this message] 2025-06-16 23:05 ` [FFmpeg-devel] [PATCH " softworkz . 2025-06-17 0:59 ` Kacper Michajlow 2025-06-17 1:46 ` softworkz . 2025-06-17 13:18 ` Kacper Michajlow 2025-06-17 13:49 ` softworkz .
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='CABPLASQiM+hf=yJKeaUtuOWkFmLnh5o8oszVYwoCVsDh8-A0Kg@mail.gmail.com' \ --to=kasper93-at-gmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=softworkz@hotmail.com \ /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