July 2022 - Wine-Devel - list.winehq.org

Re: [PATCH v2 2/4] bcrypt/tests: Test for BCryptEncrypt with RSA keys.

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120255 Your paranoid android. === debian11 (32 bit report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Arabic:Morocco report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit German report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit French report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hebrew:Israel report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hindi:India report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Japanese:Japan report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Chinese:China report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (64 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same

July 31, 2022

Re: [PATCH 2/4] bcrypt/tests: Test for BCryptEncrypt with RSA keys.

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120251 Your paranoid android. === debian11 (32 bit report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Arabic:Morocco report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit German report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit French report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hebrew:Israel report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hindi:India report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Japanese:Japan report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Chinese:China report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (64 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same

July 31, 2022

Re: [PATCH v2 1/1] cabinet.dll: implement DllGetVersion & GetDllVersion Fix stub DllGetVersion implementation to read Dll ve

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120249 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

July 31, 2022

Re: [PATCH 1/1] cabinet.dll: implement DllGetVersion & GetDllVersion Fix stub DllGetVersion implementation to read Dll versi

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120247 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w8 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w8adm (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w864 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w864 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

July 31, 2022

Re: [PATCH v2 01/11] winmm/tests: Add tests for visibility of video window.

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120234 Your paranoid android. === w8 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

July 31, 2022

Re: [PATCH v2 05/11] winmm/tests: Add tests for destination of video window.

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120238 Your paranoid android. === debian11 (32 bit report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit German report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit French report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) === debian11 (32 bit WoW report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (64 bit WoW report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51)

July 31, 2022

Re: [PATCH v2 04/11] winmm/tests: Add tests for dimensions of video window.

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120237 Your paranoid android. === debian11 (32 bit report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit German report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit French report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) === debian11 (32 bit WoW report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (64 bit WoW report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51)

July 31, 2022

Re: [PATCH v2 7/7] xactengine3_7: Return error on invalid notification value.

by Marvin

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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120222 Your paranoid android. === debian11 (32 bit report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Arabic:Morocco report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit German report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit French report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Hebrew:Israel report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Hindi:India report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Japanese:Japan report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Chinese:China report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit WoW report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (64 bit WoW report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received

July 31, 2022

Re: [PATCH] fltlib: Add fixme stub for FilterSendMessage.

by Zhiyi Zhang

On 7/21/22 17:13, Chao Long wrote: > Signed-off-by: Chao Long <longchao(a)uniontech.com> > --- > dlls/fltlib/fltlib.c | 11 +++++++++++ > dlls/fltlib/fltlib.spec | 2 +- > 2 files changed, 12 insertions(+), 1 deletion(-) > > diff --git a/dlls/fltlib/fltlib.c b/dlls/fltlib/fltlib.c > index a6cf060b3d1..a322e7559de 100644 > --- a/dlls/fltlib/fltlib.c > +++ b/dlls/fltlib/fltlib.c > @@ -80,3 +80,14 @@ HRESULT WINAPI FilterUnload(LPCWSTR filtername) > > return S_OK; > } > + > +/********************************************************************** > + * FilterSendMessage (FLTLIB.@) > + */ > +HRESULT WINAPI FilterSendMessage(HANDLE port, LPVOID in_buffer, DWORD in_size, LPVOID out_buffer, > + DWORD out_size, LPDWORD returned) > +{ > + FIXME("(%p, %p, %d, %p, %d, %p) stub\n", port,in_buffer,in_size,out_buffer,out_size,returned); Please use %ld to print DWORD. %d generates warnings. > + > + return S_OK; > +} > \ No newline at end of file Please keep a new line. Also, do you have a real world application that needs this stub? Thanks, Zhiyi > diff --git a/dlls/fltlib/fltlib.spec b/dlls/fltlib/fltlib.spec > index 226a61519d1..48caa505a28 100644 > --- a/dlls/fltlib/fltlib.spec > +++ b/dlls/fltlib/fltlib.spec > @@ -18,7 +18,7 @@ > @ stub FilterInstanceGetInformation > @ stdcall FilterLoad(wstr) > @ stub FilterReplyMessage > -@ stub FilterSendMessage > +@ stdcall FilterSendMessage(ptr ptr long ptr long ptr) > @ stdcall FilterUnload(wstr) > @ stub FilterVolumeClose > @ stub FilterVolumeFindClose

July 31, 2022

Wine staging 7.14 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.14 (537 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * xactengine3.7: Delay Notication for WAVEBANKPREPARED * ntdll: Check return parameter before use * ntdll: RtlFirstFreeAce only return FALSE on error * xactengine3_7: Remove Entry after FAudio Destroyed call Added: * None Updated: * xactengine3_7-Notification * xactengine3_7-callbacks Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

July 30, 2022