#9934 closed defect (invalid)
FFmpeg failed to runtests due to Test sub-pgs-remux failed with MSVC on windows
Reported by: | avagong | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | git-master | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
FFmpeg failed to runtests due to Test sub-pgs-remux failed with MSVC on windows.Could you please help take a look at this? Thank you!
Steps to reproduce:
1.git clone https://github.com/FFmpeg/FFmpeg.git F:\gitP\FFmpeg\FFmpeg
2.Open a VS 2019 x64 prompt and browse to F:\gitP\FFmpeg
3.cd F:\gitP\FFmpeg\FFmpeg\..\
4.set FFMPEG_SRC_PATH=F:\gitP\FFmpeg\FFmpeg
5.set FFMPEG_FATE_PATH=../fate-suite/
6.set path=F:\gitP\FFmpeg\FFmpeg\..\tools;%PATH%
7.set MSYS2_PATH_TYPE=inherit
8 .\tools\msys32\usr\bin\sh.exe --login -i -c "/F/gitP/ffmpeg/tools/build.sh"
9 .\tools\msys32\usr\bin\sh.exe --login -i -c "/F/gitP/ffmpeg/tools/test.sh"
Actual result:
Test sub-pgs-remux failed. Look at tests/data/fate/sub-pgs-remux.err for details.
make: * [tests/Makefile:307: fate-sub-pgs-remux] Error 1
make: * Waiting for unfinished jobs....
Failed FATE test suite!
Attachments (2)
Change History (7)
by , 2 years ago
Attachment: | test.log.6.out added |
---|
by , 2 years ago
comment:1 by , 2 years ago
comment:2 by , 2 years ago
I cannot reproduce - make fate and the mentioned test succeed here with MSVC and clang-cl - and the ticket looks invalid to me: Whatever it may be, I don’t think we support build.sh
comment:4 by , 2 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
This does not look like a valid ticket.
comment:5 by , 2 years ago
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20220807151248.15182-3-timo@rothenpieler.org/
So msvc is supported...
Maybe this: https://github.com/mcmtroffaes/ffmpeg-msvc-build
Just sent a patch for this: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-September/301831.html Can you test whether it works?
(It is a line-ending issue, i.e. Unix \n vs Windows \r\n. The ref file uses \n and yet strangely in your test.log.6.out it is the "-" part of the diff (that corresponds to the ref file) that has \r\n and the other part (the output of your test run) has simple \n.)