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://testbot.winehq.org/JobDetails.pl?Key=9259
Your paranoid android.
=== w8 (32 bit visual) ===
visual.c:2717: Test failed: unexpected colortable on offscreen surface
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://testbot.winehq.org/JobDetails.pl?Key=9245
Your paranoid android.
=== wvistau64 (32 bit sock) ===
sock: unhandled exception c0000005 at 00000000
> static BOOL skip_spaces(parser_ctx_t *ctx)
> {
> - while(ctx->ptr < ctx->end && isspaceW(*ctx->ptr)) {
> + while(ctx->ptr < ctx->end && (isspaceW(*ctx->ptr) || *ctx->ptr == 0xFEFF /* UTF16 BOM */)) {
> if(is_endline(*ctx->ptr++))
> ctx->nl = TRUE;
> }
This looks correct according to ECMA-252 section 7.2 - all of the
following is a whitespace:
- tab and vertical tab, 0x9 and 0xb;
- …
[View More]form feed 0xc
- space 0x20
- NBSP 0xa0
- UTF-16 BOM 0xfeff
- any other Unicode "space separator"
Hopefully isspaceW() covers everything but the BOM. What worries me is
that isspaceW() itself is used in numerous places in code on its own. So
probably we need more tests to cover more cases where space separators
could be used, and later have our own is_space() call that will conform
to the standard.
[View Less]
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://testbot.winehq.org/JobDetails.pl?Key=9217
Your paranoid android.
=== w7u (32 bit msg) ===
msg.c:11961: Test failed: got message 102
msg.c:11966: Test failed: bad wparam 201a/2260
msg.c:11978: Test failed: bad wparam 201a/2260
msg.c:11985: Test failed: no …
[View More]messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:11987: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:11994: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:11996: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12003: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12005: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12012: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12014: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12021: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12023: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12031: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12034: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12039: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12041: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12049: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12057: Test failed: bad wparam 201a/2260
msg.c:12061: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12069: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12071: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12073: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12082: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12085: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12087: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12093: Test failed: no messages: 0: the msg sequence is not complete: expected 0000 - actual 0102
msg.c:12095: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12097: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a
msg.c:12102: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam 0x2260 got 0x201a0081
msg.c:12111: Test failed: bad wparam 81/30fb
msg.c:12118: Test failed: bad wparam 81/30fb
msg.c:12129: Test failed: bad wparam 3f/81
msg.c:12131: Test failed: no message
msg.c:12134: Test failed: bad wparam 3f/81
msg.c:12144: Test failed: bad wparam 3f/81
msg.c:12150: Test failed: unexpected hwnd 00060150
msg.c:12152: Test failed: bad wparam 81/81
msg.c:12161: Test failed: bad wparam 3f/81
msg.c:12168: Test failed: unexpected hwnd 00000000
msg.c:12170: Test failed: bad wparam 81/81
msg.c:12171: Test failed: bad lparam 0
msg.c:12183: Test failed: bad wparam 3f/81
msg.c:12188: Test failed: bad wparam 3f/81
msg.c:12190: Test failed: no message
msg.c:12193: Test failed: bad wparam 3f/81
msg.c:12195: Test failed: no message
msg.c:12198: Test failed: bad wparam 3f/81
[View Less]
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://testbot.winehq.org/JobDetails.pl?Key=9214
Your paranoid android.
=== wvistau64 (32 bit ordinal) ===
ordinal.c:548: Test failed: SHMapHandle failed: 6
ordinal.c:551: Test failed: SHLockShared failed: 87
ordinal.c:557: Test failed: SHUnlockShared failed: 487
=== …
[View More]w2008s64 (32 bit ordinal) ===
ordinal.c:548: Test failed: SHMapHandle failed: 6
ordinal.c:551: Test failed: SHLockShared failed: 87
ordinal.c:557: Test failed: SHUnlockShared failed: 487
=== wvistau64 (64 bit ordinal) ===
ordinal.c:548: Test failed: SHMapHandle failed: 6
ordinal.c:551: Test failed: SHLockShared failed: 87
ordinal.c:557: Test failed: SHUnlockShared failed: 487
=== w2008s64 (64 bit ordinal) ===
ordinal.c:548: Test failed: SHMapHandle failed: 6
ordinal.c:551: Test failed: SHLockShared failed: 87
ordinal.c:557: Test failed: SHUnlockShared failed: 487
[View Less]
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://testbot.winehq.org/JobDetails.pl?Key=9213
Your paranoid android.
=== wvistau64 (32 bit ordinal) ===
ordinal.c:549: Test failed: SHMapHandle failed: 6
ordinal.c:553: Test failed: SHLockShared failed: 87
ordinal.c:560: Test failed: SHUnlockShared failed: 487
=== …
[View More]w2008s64 (32 bit ordinal) ===
ordinal.c:549: Test failed: SHMapHandle failed: 6
ordinal.c:553: Test failed: SHLockShared failed: 87
ordinal.c:560: Test failed: SHUnlockShared failed: 487
=== wvistau64 (64 bit ordinal) ===
ordinal.c:549: Test failed: SHMapHandle failed: 6
ordinal.c:553: Test failed: SHLockShared failed: 87
ordinal.c:560: Test failed: SHUnlockShared failed: 487
=== w2008s64 (64 bit ordinal) ===
ordinal.c:549: Test failed: SHMapHandle failed: 6
ordinal.c:553: Test failed: SHLockShared failed: 87
ordinal.c:560: Test failed: SHUnlockShared failed: 487
[View Less]
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://testbot.winehq.org/JobDetails.pl?Key=9211
Your paranoid android.
=== w2000pro (32 bit) ===
No test summary line found
=== wxppro (32 bit) ===
No test summary line found
=== wvistau64 (32 bit) ===
No test summary line found
=== w2008s64 (32 bit) ===
No test …
[View More]summary line found
=== w7u (32 bit) ===
No test summary line found
=== w8 (32 bit) ===
No test summary line found
=== wvistau64 (64 bit) ===
No test summary line found
=== w2008s64 (64 bit) ===
No test summary line found
[View Less]
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://testbot.winehq.org/JobDetails.pl?Key=9210
Your paranoid android.
=== w2000pro (32 bit) ===
No test summary line found
=== wxppro (32 bit) ===
No test summary line found
=== wvistau64 (32 bit) ===
No test summary line found
=== w2008s64 (32 bit) ===
No test …
[View More]summary line found
=== w7u (32 bit) ===
No test summary line found
=== w8 (32 bit) ===
No test summary line found
=== wvistau64 (64 bit) ===
No test summary line found
=== w2008s64 (64 bit) ===
No test summary line found
[View Less]
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://testbot.winehq.org/JobDetails.pl?Key=9200
Your paranoid android.
=== wvistau64 (32 bit file) ===
file.c:367: Test failed: attributes of file "testfile.xxx" are 0x0820
=== wvistau64 (64 bit file) ===
file.c:367: Test failed: attributes of file "testfile.xxx" are 0x0820
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://testbot.winehq.org/JobDetails.pl?Key=9199
Your paranoid android.
=== wvistau64 (32 bit file) ===
file.c:367: Test failed: attributes of file "testfile.xxx" are 0x0820
=== wvistau64 (64 bit file) ===
file.c:367: Test failed: attributes of file "testfile.xxx" are 0x0820