16 Jun
2023
16 Jun
'23
2:42 a.m.
On Fri Jun 16 02:36:44 2023 +0000, **** wrote:
Marvin replied on the mailing list:
Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=133836 Your paranoid android. === debian11 (32 bit report) === mf: transform.c:6395: Test failed: wmvdec: Flush returned 0xd0000005. transform.c:6397: Test failed: wmvdec: Flush returned 0xd0000005. transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4339: Test failed: ProcessMessage returned 0xd0000005 transform.c:4402: Test failed: GetElementCount returned 0x62 transform.c:4404: Test failed: sample 97: got 1 buffers transform.c:4404: Test failed: sample 97: got sample time 38800000 transform.c:4404: Test failed: sample 97: got sample duration 400000 transform.c:1090: Test failed: sample 97: buffer 0: got unexpected buffer Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00426c12). Report validation errors: mf:transform prints too much data (45269 bytes)
How trustworthy are these reports? There seems to be a lot of seemingly unrelated failures in d3d in the report. Looking into the transform tests.