Re: [2/4] dnsapi/tests: Compile with -D__WINESRC__.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2733 Your paranoid android. === wxppro (32 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === wvista (32 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === w2008s64 (32 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === w7pro64 (32 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === w864 (32 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === w2008s64 (64 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === w7pro64 (64 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly === w864 (64 bit record) === record.c:46: Test failed: succeeded unexpectedly record.c:49: Test failed: succeeded unexpectedly
Re: dlls/explorerframe: build tests with -D__WINESRC__
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2750 Your paranoid android. === wvista (32 bit nstc) === nstc.c:1934: Test failed: Got event 7, count 0 nstc.c:1936: Test failed: Got event 4, count 0 nstc.c:1949: Test failed: Got event 4, count 0
Re: winmm/tests: Use BOOL type where appropriate
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2721 Your paranoid android. === wxppro (32 bit wave) === wave.c:498: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 13211 bytes, should be 13230 wave.c:498: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 13229 bytes, should be 13230 wave.c:498: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 13075 bytes, should be 13230 wave.c:509: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 13091 samples (13091 bytes), should be 13230 (13230 bytes) wave.c:522: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 594 ms, (13108 bytes), should be 600 (13230 bytes) wave.c:498: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 13220 bytes, should be 13230 wave.c:498: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 17621 bytes, should be 17640 wave.c:509: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 17634 samples (17634 bytes), should be 17640 (17640 bytes) wave.c:498: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 22016 bytes, should be 22050 wave.c:509: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 22027 samples (22027 bytes), should be 22050 (22050 bytes) wave.c:522: Test failed: waveOutGetPosition(WAVE_MAPPER): returned 999 ms, (22044 bytes), should be 1000 (22050 bytes)
Re: ieframe: Compile tests with __WINESRC__ define.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2688 Your paranoid android. === wxppro (32 bit webbrowser) === webbrowser.c:792: Test failed: ReadyState = 1, expected 4
Re: mshtml: Compile tests with __WINESRC__ define.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2689 Your paranoid android. === w864 (64 bit activex) === activex.c:1346: Test failed: unexpected call SetObjectRects === wxppro (32 bit htmldoc) === htmldoc.c:2898: Test failed: mon(0026BFD0) != exmon(00269670) htmldoc.c:7601: Test failed: mon(0026BFD0) != exmon(00269670) htmldoc.c:5978: Test failed: mon(0026BFD0) != exmon(00269670) htmldoc.c:2898: Test failed: mon(0029CA28) != exmon(00286FF8) htmldoc.c:7601: Test failed: mon(0029CA28) != exmon(00286FF8) htmldoc.c:5978: Test failed: mon(0029CA28) != exmon(00286FF8) === wvista (32 bit htmldoc) === No test summary line found === w7pro64 (32 bit htmldoc) === No test summary line found
Re: ddraw/tests: Use BOOL type where appropriate
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2682 Your paranoid android. === wxppro (32 bit d3d) === d3d.c:1261: Test failed: Homogeneous output was generated despite UNCLIPPED flag === wvista (32 bit d3d) === d3d.c:1261: Test failed: Homogeneous output was generated despite UNCLIPPED flag === w2008s64 (32 bit d3d) === d3d.c:1261: Test failed: Homogeneous output was generated despite UNCLIPPED flag === w7pro64 (32 bit d3d) === d3d.c:1261: Test failed: Homogeneous output was generated despite UNCLIPPED flag
Re: kernel32/tests: Add tests for job objects (try 7)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2683 Your paranoid android. === w864 (64 bit process) === process.c:2092: Test failed: Unexpected completion event: 6, 0158, 02F0
Re: msi/tests: Use BOOL type where appropriate (resend)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2667 Your paranoid android. === wvista (32 bit msi) === Timeout === w2008s64 (32 bit msi) === Timeout Failure running script in VM: network read timed out === w2008s64 (64 bit msi) === Timeout
Re: gdi32/tests: Skip linked font like SimSun-ExtB in fixed-pitch font selection.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2669 Your paranoid android. === wvista (32 bit font) === The test timed out === w2008s64 (32 bit font) === Timeout Failure running script in VM: network read timed out
Re: ws2_32/tests: Use BOOL type where appropriate
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2674 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (bc): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 71AB8D62 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (2c8): unexpectedly at the OOB mark: 0 === w7pro64 (32 bit sock) === sock.c:509: Test failed: oob_server (8a4): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (8a4): unexpectedly at the OOB mark: 0 === w864 (32 bit sock) === sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1740: Test failed: getservbyname could not retrieve information for domain:
Re: [PATCH 3/3] msvcrt: Add support for vtordispex demangling
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2650
Your paranoid android.
=== wxppro (32 bit cpp) ===
cpp.c:1328: Test failed: 124: Got name [thunk]: __thiscall
CView::`vcall'{392,{flat}}'
cpp.c:1331: Test failed: 124: Expected [thunk]: __thiscall
CView::`vcall'{392,{flat}}' }'
cpp.c:1328: Test failed: 125: Got name
?_dispatch@_impl_Engine@SalomeApp@@$R4CE@BA@PPPM@7AE_NAAVomniCallHandle@@@Z
cpp.c:1331: Test failed: 125: Expected [thunk]:public: virtual bool __thiscall
SalomeApp::_impl_Engine::_dispatch`vtordispex{36,16,4294967292,8}' (class
omniCallHandle )
Re: [PATCH 2/3] msvcrt: Add support for vcall thunks demangling
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2649
Your paranoid android.
=== wxppro (32 bit cpp) ===
cpp.c:1326: Test failed: 124: Got name [thunk]: __thiscall
CView::`vcall'{392,{flat}}'
cpp.c:1329: Test failed: 124: Expected [thunk]: __thiscall
CView::`vcall'{392,{flat}}' }'
Re: [PATCH 2/3] msvcrt: Add support for vcall thunks demangling (try2)
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2651
Your paranoid android.
=== wxppro (32 bit cpp) ===
cpp.c:1329: Test failed: 125: Got name
?_dispatch@_impl_Engine@SalomeApp@@$R4CE@BA@PPPM@7AE_NAAVomniCallHandle@@@Z
cpp.c:1332: Test failed: 125: Expected [thunk]:public: virtual bool __thiscall
SalomeApp::_impl_Engine::_dispatch`vtordispex{36,16,4294967292,8}' (class
omniCallHandle )
Re: msi/tests: Use BOOL type where appropriate
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2660 Your paranoid android. === wvista (32 bit msi) === The test timed out === w2008s64 (32 bit msi) === The test timed out === w7pro64 (32 bit msi) === No test summary line found Failure running script in VM: network read timed out === w2008s64 (64 bit msi) === Timeout === w7pro64 (64 bit msi) === Timeout
Re: kernel32/tests: Fix compilation on systems that don't support nameless unions.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2634 Your paranoid android. === w7pro64 (64 bit comm) === comm.c:861: Test failed: WaitCommEvent failed with a timeout comm.c:872: recovering after WAIT_TIMEOUT... comm.c:883: Test failed: WaitCommEvent error 0 comm.c:885: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:889: WaitCommEvent for EV_TXEMPTY took 1014 ms (timeout 1000) comm.c:891: Test failed: WaitCommEvent used 1014 ms for waiting
Re: mshtml/tests: Fix compilation on systems that don't support nameless unions.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2637 Your paranoid android. === wxppro (32 bit htmldoc) === htmldoc.c:2898: Test failed: mon(0026BF78) != exmon(00269670) htmldoc.c:7601: Test failed: mon(0026BF78) != exmon(00269670) htmldoc.c:5978: Test failed: mon(0026BF78) != exmon(00269670) htmldoc.c:2898: Test failed: mon(002ADFE8) != exmon(00265FE8) htmldoc.c:7601: Test failed: mon(002ADFE8) != exmon(00265FE8) htmldoc.c:5978: Test failed: mon(002ADFE8) != exmon(00265FE8) === wvista (32 bit htmldoc) === No test summary line found === w7pro64 (32 bit htmldoc) === No test summary line found
Re: [PATCH 2/2] advapi32: Don't cache HKCR if WOW64 redirection flags are set
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2624 Your paranoid android. === wxppro (32 bit registry) === Timeout
Re: [PATCH 5/5] wininet: Added InternetLockRequestFile tests.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2625 Your paranoid android. === w2008s64 (64 bit http) === http.c:3521: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3521: Test failed: HttpQueryInfo failed 0
Re: [5/5] gdi32: Don't modify output glyph metrics unless the function succeeds. (resend)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2426 Your paranoid android. === wvista (32 bit font) === The test timed out === w2008s64 (32 bit font) === Failure running script in VM: network read timed out === w2008s64 (64 bit font) === Failure running script in VM: network read timed out
Re: Assorted spelling fixes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2429 Your paranoid android. === build (build) === Patch failed to apply
Re: Assorted spelling fixes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2431 Your paranoid android. === build (build) === Patch failed to apply
Re: Re: kernel32/tests: Fix the test_waittxempty() timeout.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2434 Your paranoid android. === wxppro (32 bit comm) === comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... No test summary line found Failure running script in VM: network read timed out === w2008s64 (32 bit comm) === comm.c:1670: test_AbortWaitCts timeout 500 handle 00C4 comm.c:1637: Changing CommMask on the fly for handle 00C4 after timeout 500 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 No test summary line found Failure running script in VM: network read timed out === w7pro64 (32 bit comm) === comm.c:1670: test_AbortWaitCts timeout 500 handle 0130 comm.c:1637: Changing CommMask on the fly for handle 0130 after timeout 500 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1094: Test failed: WriteFile failed with a timeout comm.c:1096: Test failed: GetOverlappedResult reported error 996 comm.c:1097: Test failed: expected 64000, written 0 Timeout === w2008s64 (64 bit comm) === comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 Timeout === w7pro64 (64 bit comm) === comm.c:887: WaitCommEvent for EV_TXEMPTY took 0 ms (timeout 1000) comm.c:1670: test_AbortWaitCts timeout 500 handle 00CC comm.c:1637: Changing CommMask on the fly for handle 00CC after timeout 500 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:1064: Test failed: WaitCommEvent failed with a timeout comm.c:1075: recovering after WAIT_TIMEOUT... comm.c:1086: Test failed: WaitCommEvent error 0 comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 Timeout
Re: Assorted spelling fixes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2430 Your paranoid android. === build (build) === Patch failed to apply
Re: Assorted spelling fixes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2433 Your paranoid android. === build (build) === Patch failed to apply
Re: Assorted spelling fixes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2432 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 4/7] msvcr90/tests: Use the W form of CreateEvent().
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2457 Your paranoid android. === wxppro (32 bit msvcr90) === No test summary line found
Re: [PATCH 2/7] qedit/tests: Use the W version of FindResource().
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2455 Your paranoid android. === w2008s64 (32 bit mediadet) === mediadet.c:149: Test failed: CoCreateInstance failed: 80040154 mediadet: unhandled exception c005 at 0040184A === w2008s64 (64 bit mediadet) === mediadet.c:149: Test failed: CoCreateInstance failed: 80040154 mediadet: unhandled exception c005 at 004017A3
Re: [1/2] gdi32: Fix the B spacing value of empty glyph. (try 3)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2605 Your paranoid android. === wvista (32 bit font) === The test timed out === w2008s64 (32 bit font) === Failure running script in VM: network read timed out
Re: [2/5] ws2_32: Always clear res on error in getaddrinfo/GetAddrInfoW.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2607 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (108): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 71AB8D62 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (7c4): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 74AA9799 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (470): unexpectedly at the OOB mark: 0
Re: [3/5] ws2_32: Add some tests for getpeername.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2608 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (c8): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 71AB8D62 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (320): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 74AA9799 === w2008s64 (64 bit sock) === sock.c:509: Test failed: oob_server (808): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (808): unexpectedly at the OOB mark: 0
Re: [4/5] ws2_32: Return an error from accept if the address buffer is too small.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2609 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (c8): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (520): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 74AA9799 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (78c): unexpectedly at the OOB mark: 0
Re: [5/5] ws2_32: Always return the source address from WSAAccept.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2610 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (c8): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (618): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 74AA9799 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (600): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at
Re: ws2_32: Implement WSASendMsg() (try 3)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2414 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (210): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 71AB8D62 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (5a0): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (6b0): unexpectedly at the OOB mark: 0
Re: [1/3] ws2_32: Always clear res on error in getaddrinfo/GetAddrInfoW.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2419 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (2a4): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (774): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (884): unexpectedly at the OOB mark: 0 === w7pro64 (64 bit sock) === sock.c:509: Test failed: oob_server (af8): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (af8): unexpectedly at the OOB mark: 0 sock.c:288: Test failed: do_synchronous_recv (af8): error 10054: sock.c:534: Test failed: oob_server (af8): not at the OOB mark: 1
Re: [2/3] ws2_32: Return an error from accept if the address buffer is too small.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2420 Your paranoid android. === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (5a0): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 757A9799 === w7pro64 (32 bit sock) === sock.c:528: Test failed: oob_server (778): not at the OOB mark: 1 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (7f8): unexpectedly at the OOB mark: 0
Re: [3/3] ws2_32: Always return the source address from WSAAccept.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2421 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (b0): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 71AB8D62 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (5a0): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (624): unexpectedly at the OOB mark: 0
Re: mshtml: Added support for 'document' and 'window' script for attribute values.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2427 Your paranoid android. === build (build) === Patch failed to apply
Re: mmdevapi/tests: test MMDevPropStore_GetAt
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2403 Your paranoid android. === wvista (32 bit propstore) === propstore.c:108: Test failed: DEVPKEY_Device_FriendlyName not found
Re: [1/2] ws2_32/tests: Fix an ok() call comment
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2387 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (408): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:509: Test failed: oob_server (bb8): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (bb8): unexpectedly at the OOB mark: 0 === w7pro64 (32 bit sock) === sock.c:528: Test failed: oob_server (6f0): not at the OOB mark: 1 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (940): unexpectedly at the OOB mark: 0
Re: [2/2] ws2_32: Implement WSASendMsg()
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2388 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (1c4): unexpectedly at the OOB mark: 0 === w7pro64 (32 bit sock) === sock.c:509: Test failed: oob_server (870): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (870): unexpectedly at the OOB mark: 0 sock.c:288: Test failed: do_synchronous_recv (870): error 10054: sock.c:534: Test failed: oob_server (870): not at the OOB mark: 1
Re: add ualapi directory (try 12)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2391 Your paranoid android. === build (build) === Missing build status line The build timed out
Re: [1/3] ws2_32/tests: Fix an ok() call comment
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2392 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (748): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (998): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at === w7pro64 (32 bit sock) === sock.c:509: Test failed: oob_server (2f0): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (2f0): unexpectedly at the OOB mark: 0 sock.c:288: Test failed: do_synchronous_recv (2f0): error 10054: sock.c:534: Test failed: oob_server (2f0): not at the OOB mark: 1 === w2008s64 (64 bit sock) === sock.c:509: Test failed: oob_server (938): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (938): unexpectedly at the OOB mark: 0 sock: unhandled exception c005 at 07FEFE229CD9
Re: [3/3] ws2_32: Implement WSASendMsg() (try 2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2393 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (1d0): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (5a0): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:509: Test failed: oob_server (b64): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (b64): unexpectedly at the OOB mark: 0 === w7pro64 (64 bit sock) === sock.c:509: Test failed: oob_server (650): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (650): unexpectedly at the OOB mark: 0 sock.c:288: Test failed: do_synchronous_recv (650): error 10054: sock.c:534: Test failed: oob_server (650): not at the OOB mark: 1
Re: [2/3] gdi32: Return fake BBox when requested empty glyph metrics. (try 2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2351 Your paranoid android. === w7u (32 bit font) === The test timed out
Re: ntdll: Make asynchronous WaitCommEvent report correct number of bytes returned.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2356 Your paranoid android. === build (build) === Patch failed to apply
Re: add ualapi directory (try 10)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2370 Your paranoid android. === build (build) === Make failed
Re: [PATCH 2/2] mshtml: Added IHTMLFormElement::sumit tests.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2374 Your paranoid android. === build (build) === Patch failed to apply
Re: (try 6)[3/5] imm32: use thread data from target HWND
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2375 Your paranoid android. === build (build) === Patch failed to apply
Re: (try 6)[4/5] imm32: Restrict crossthread Association and destruction
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2376 Your paranoid android. === build (build) === Patch failed to apply
Re: (try 6)[5/5] imm32: limit cross thread access to ImmSet* functions
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2377 Your paranoid android. === build (build) === Patch failed to apply
Re: add ualapi directory (try 11)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2386 Your paranoid android. === build (build) === Make failed
Re: [2/2] oledb32: Implement IDataSourceLocator get/put hWnd (try 2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2338 Your paranoid android. === build (build) === Patch failed to apply
Re: ntdll: Perform the offset checks in NtWriteFile also for a serial device.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2339 Your paranoid android. === build (build) === Patch failed to apply
Re: dlls: Replace the remaining CONSTs.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2341 Your paranoid android. === build (build) === Patch failed to apply
Re: dlls: Replace the remaining CONSTs.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2343 Your paranoid android. === build (build) === Patch failed to apply
Re: dlls: Replace the remaining CONSTs.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2344 Your paranoid android. === build (build) === Patch failed to apply
Re: kernel32/tests: Add DuplicateHandle test to the file access tests.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2345 Your paranoid android. === build (build) === Patch failed to apply
Re: dlls: Replace the remaining CONSTs.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2340 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 2/2] msvcrt: Call MSVCRT_strtoi64_l in strtoul implementation
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2346 Your paranoid android. === build (build) === Patch failed to apply
Re: dlls: Replace the remaining CONSTs.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2342 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 3/3] msvcrt: Call MSVCRT_strtoi64_l in strtoul implementation (try2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2349 Your paranoid android. === build (build) === Patch failed to apply
Re: [1/3] gdi32: Return GDI_ERROR when requested empty glyph bitmaps. (try 2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2350 Your paranoid android. === w7u (32 bit font) === No test summary line found Failure running script in VM: network read timed out
Re: [3/3] gdi32: Don't modify output glyph metrics unless the function succeeds. (try 2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2352 Your paranoid android. === build (build) === Patch failed to apply
Re: user32: Avoid using CONST.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2332 Your paranoid android. === build (build) === Patch failed to apply
Re: add ualapi directory (try 9
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2313 Your paranoid android. === build (build) === Missing build status line The build timed out
Re: [1/2] winhttp/tests: Remove explicit zero-intialization of static data.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2314 Your paranoid android. === build (build) === Patch failed to apply
Re: advapi32/tests: Mark a test result as broken.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2315 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 5/5] ddraw: Avoid VOID.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2316 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 3/5] d3d9/tests: Add a volume V16U16 test.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2317 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 4/5] d3d8/tests: Add a volume V16U16 test.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2318 Your paranoid android. === build (build) === Patch failed to apply
Re: [2/2] oleaut32: LoadRegTypeLib() should check actual typelib version
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2330 Your paranoid android. === build (build) === Patch failed to apply
Re: add ualapi directory (try 5)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2309 Your paranoid android. === build (build) === Missing build status line The build timed out
Re: add ualapi directory (try 7)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2310 Your paranoid android. === build (build) === Make failed
Re: add ualapi directory (try 8)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2311 Your paranoid android. === build (build) === Make failed
Re: [3/4] kernel32/tests: Add 0-length read tests for a pipe.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2250 Your paranoid android. === wvista (32 bit pipe) === Failure running script in VM: network read error: Resource temporarily unavailable
Re: ntdll: Perform the offset checks also for a serial device.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2267 Your paranoid android. === w7pro64 (32 bit comm) === comm.c:863: Test failed: WaitCommEvent failed with a timeout comm.c:875: recovering after WAIT_TIMEOUT... comm.c:886: Test failed: WaitCommEvent error 0 comm.c:888: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:892: WaitCommEvent for EV_TXEMPTY took 1014 ms (timeout 1000) comm.c:894: Test failed: WaitCommEvent used 1014 ms for waiting comm.c:1561: test_AbortWaitCts timeout 500 handle 00F8 comm.c:1528: Changing CommMask on the fly for handle 00F8 after timeout 500
Re: [PATCH] oleaut32: Implement ICreateTypeInfo::SetFuncDocString
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2280 Your paranoid android. === build (build) === Patch failed to apply
Re: [2/3] d3d9/tests: Test if IDirect3DSwapChain9Ex is available with IDirect3D9(Ex)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2281 Your paranoid android. === build (build) === Patch failed to apply
Re: [3/3] d3d9/tests: Implemented tests for IDirect3DSwapChain9Ex_GetDisplayModeEx
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2282 Your paranoid android. === build (build) === Patch failed to apply
Re: ws2_32: ConnectEx should not work on unbound socket
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2286 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 1/5] ddraw/tests: Add a test for render target surface capabilities.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2289 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 5/5] d3d9: Avoid CONST.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2290 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 5/6] d3d8/tests: Add a volume V16U16 test.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2292 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 4/6] d3d9/tests: Add a volume V16U16 test.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2291 Your paranoid android. === build (build) === Patch failed to apply
Re: Re: add ualapi directory (try 3)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2304 Your paranoid android. === build (build) === Make failed
Re: add ualapi directory (try 4)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2308 Your paranoid android. === build (build) === Make failed
Re: [4/4] kernel32: Remove a 0-length read optimization from ReadFile. Resend.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2251 Your paranoid android. === build (build) === Patch failed to apply
Re: [4/4] kernel32: Remove a 0-length read optimization from ReadFile. Resend.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2252 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 4/5] d3d9/tests: Add tests for block-based volume formats (try 2).
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2253 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 5/5] d3d9/tests: Test invalid volume lock boxes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2254 Your paranoid android. === build (build) === Patch failed to apply
Re: wininet: Don't assume that end of chunk means end of stream. (try 2)
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2255 Your paranoid android. === build (build) === Patch failed to apply
Re: [3/4] imm32: use thread data from target HWND
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2256 Your paranoid android. === build (build) === Patch failed to apply
Re: [4/4] imm32: Prevent assocating cross thread default contexts
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2257 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 2/2] d3dx9/tests: Add matrix column register count clamp test.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2259 Your paranoid android. === build (build) === Patch failed to apply
Re: (resend)[3/4] imm32: use thread data from target HWND
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2262 Your paranoid android. === build (build) === Patch failed to apply
Re: (resend)[3/4] imm32: use thread data from target HWND
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2263 Your paranoid android. === build (build) === Patch failed to apply
Re: shlwapi/tests: Fix stream test failures under some win2000 versions.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2266 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 1/5] d3d9/tests: Read the caps from the device.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2268 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 5/5] d3d8/tests: Test invalid volume lock boxes.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2270 Your paranoid android. === build (build) === Patch failed to apply
Re: [PATCH 4/5] d3d8/tests: Add tests for block-based volume formats.
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2269 Your paranoid android. === build (build) === Patch failed to apply
