[Bug 52072] New: winmm:mci fails in wow64 Wine
https://bugs.winehq.org/show_bug.cgi?id=52072 Bug ID: 52072 Summary: winmm:mci fails in wow64 Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- winmm:mci started failing in wow64 Wine on 2021-11-11. It now has 51 failures: mci.c:248: Test failed: status 4(mode): MCIERR_UNSUPPORTED_FUNCTION mci.c:328: Test failed: status mode: MCIERR_UNSUPPORTED_FUNCTION mci.c:656: Test marked todo: mci info new file returned 0=NOERROR mci.c:660: Test marked todo: status x length initial: MCIERR_UNSUPPORTED_FUNCTION mci.c:665: Test failed: mci status samplespersec returned MCIERR_UNSUPPORTED_FUNCTION mci.c:732: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:781: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:812: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:827: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:848: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:849: Test failed: mci status mode: after play from 0 to 0 mci.c:860: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:903: Test failed: mci status position notify returned MCIERR_UNSUPPORTED_FUNCTION mci.c:906: Test failed: Expect message 0001 from status position mci.c:909: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:910: Test failed: mci status mode: mci.c:915: Test marked todo: Expect message 0001 from play to 250 wait notify mci.c:955: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:956: Test failed: mci status mode: mci.c:974: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:975: position after Sleep: ms [...] https://test.winehq.org/data/patterns.html#winmm:mci Note that besides the test failures the "mci status mode: " and "position after Sleep: ms" messages are suspicious. All four Linux test machines are impacted by this: the failure test pattern makes it obvious for cw-gtx560, cw-rx460 and the TestBot's debiant2 VM. fg-deb64 is impacted as well but it is masked by the preexisting timeout. Strangely a bisect shows that these failures started with this commit: commit 7c5761ed40f0b8cead7fa837b745b687d5df67d8 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Nov 11 16:21:00 2021 +0100 wrc: Ignore the target option. Nothing in resource files depends on the pointer size. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52072 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |7c5761ed40f0b8cead7fa837b74 | |5b687d5df67d8 Keywords| |regression, source, | |testcase -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52072 --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- That's surprising. Are you sure that everything was rebuilt correctly? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52072 --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- These days I do a make clean between each bisection step because without it builds tend to fail with all the churn that's going on. Then I check again that I can reproduce the issue with the bisected commit, and that it does not happen with the previous commit. But just to be sure I double-checked with two builds from scratch and the result holds: I can reproduce the issue with 7c5761ed40f0 but not with 6ebcc54a5c2c. That said maybe it's some uninitialized data that's now getting a bad value because the memory layout changed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52072 --- Comment #3 from Alexandre Julliard <julliard(a)winehq.org> --- You are right, my grep missed the MCI_INTEGER64 thing. Fix coming shortly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52072 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |acecec4a2e4b77cc05b0355a799 | |af20fbdc6ec49 --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> --- Fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52072 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.23. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla