February 2016 - Wine-Devel - list.winehq.org

Re: [PATCH 2/3] ntdll: Improve invalid parameter handling in NtAccessCheck. (try 2)
by Marvin Feb. 17, 2016

Feb. 17, 2016

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=20603 Your paranoid android. === w1064 (32 bit security) === security.c:3892: Test failed: MACHINE\Software owner SID (S-1-5-18) != Administrators SID (S-1-5-32-544). security.c:3933: Test failed: Builtin Users ACE has unexpected flags (0x12 != 0xa) security.c:3937: Test failed: Builtin Users ACE has unexpected mask (0x20019 != 0x80000000) security.c:3946: Test failed: Builtin Admins ACE has unexpected flags (0x12 != 0x0)

1 0

Re: [PATCH 2/2] ntdll: Improve invalid paramater handling in NtAccessCheck.
by Sebastian Lackner Feb. 17, 2016

Feb. 17, 2016

On 15.02.2016 21:53, Qian Hong wrote: > > Signed-off-by: Qian Hong <qhong(a)codeweavers.com> > --- > dlls/advapi32/tests/security.c | 4 ---- > dlls/ntdll/sec.c | 11 ++++++++++- > 2 files changed, 10 insertions(+), 5 deletions(-) > > > > 0002-ntdll-Improve-invalid-paramater-handling-in-NtAccessCh.txt > > > diff --git a/dlls/advapi32/tests/security.c b/dlls/advapi32/tests/security.c > index 69c0f77..08666dd 100644 > --- a/dlls/advapi32/tests/security.c > +++ b/dlls/advapi32/tests/security.c > @@ -1429,10 +1429,8 @@ static void test_AccessCheck(void) > ret = AccessCheck(SecurityDescriptor, Token, KEY_READ, &Mapping, > 0, &PrivSetLen, &Access, &AccessStatus); > err = GetLastError(); > -todo_wine > ok(!ret && err == ERROR_INSUFFICIENT_BUFFER, "AccessCheck should have " > "failed with ERROR_INSUFFICIENT_BUFFER, instead of %d\n", err); > -todo_wine > ok(PrivSetLen == sizeof(PRIVILEGE_SET), "PrivSetLen returns %d, expects %d\n", PrivSetLen, sizeof(PRIVILEGE_SET)); > ok(Access == 0x1abe11ed && AccessStatus == 0x1abe11ed, > "Access and/or AccessStatus were changed!\n"); > @@ -1444,10 +1442,8 @@ todo_wine > ret = AccessCheck(SecurityDescriptor, Token, KEY_READ, &Mapping, > PrivSet, &PrivSetLen, &Access, &AccessStatus); > err = GetLastError(); > -todo_wine > ok(!ret && err == ERROR_INSUFFICIENT_BUFFER, "AccessCheck should have " > "failed with ERROR_INSUFFICIENT_BUFFER, instead of %d\n", err); > -todo_wine > ok(Access == 0x1abe11ed && AccessStatus == 0x1abe11ed, > "Access and/or AccessStatus were changed!\n"); > > diff --git a/dlls/ntdll/sec.c b/dlls/ntdll/sec.c > index 125c86e..c32ae0c 100644 > --- a/dlls/ntdll/sec.c > +++ b/dlls/ntdll/sec.c > @@ -1586,7 +1586,16 @@ NtAccessCheck( > SecurityDescriptor, ClientToken, DesiredAccess, GenericMapping, > PrivilegeSet, ReturnLength, GrantedAccess, AccessStatus); > > - if (!PrivilegeSet || !ReturnLength) > + if (!ReturnLength) > + return STATUS_ACCESS_VIOLATION; > + > + if (*ReturnLength == 0) > + { > + *ReturnLength = sizeof(PRIVILEGE_SET); > + return STATUS_BUFFER_TOO_SMALL; > + } This looks a bit hacky. The code below assumes that *ReturnLength > FIELD_OFFSET( PRIVILEGE_SET, Privilege ), so it would be interesting to know what happens for sizes 0 ... 8. > + > + if (!PrivilegeSet) > return STATUS_ACCESS_VIOLATION; > > SERVER_START_REQ( access_check ) > > >

3 2

Re: [PATCH 1/3] advapi32/tests: Add more invalid parameter tests for AccessCheck.
by Marvin Feb. 17, 2016

Feb. 17, 2016

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=20602 Your paranoid android. === w1064 (32 bit security) === security.c:3905: Test failed: MACHINE\Software owner SID (S-1-5-18) != Administrators SID (S-1-5-32-544). security.c:3946: Test failed: Builtin Users ACE has unexpected flags (0x12 != 0xa) security.c:3950: Test failed: Builtin Users ACE has unexpected mask (0x20019 != 0x80000000) security.c:3959: Test failed: Builtin Admins ACE has unexpected flags (0x12 != 0x0)

1 0

Re: [PATCH] gdi32: Remove no-op abs(3) call.
by Huw Davies Feb. 17, 2016

Feb. 17, 2016

On Tue, Feb 16, 2016 at 01:55:34PM -0700, Charles Davis wrote: > Signed-off-by: Charles Davis <cdavis5x(a)gmail.com> > --- > dlls/gdi32/pen.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/dlls/gdi32/pen.c b/dlls/gdi32/pen.c > index 2ae2f2b..6793934 100644 > --- a/dlls/gdi32/pen.c > +++ b/dlls/gdi32/pen.c > @@ -195,7 +195,7 @@ HPEN WINAPI ExtCreatePen( DWORD style, DWORD width, > if (logbrush.lbStyle == BS_DIBPATTERN) logbrush.lbStyle = BS_DIBPATTERNPT; > > penPtr->logpen.elpPenStyle = style; > - penPtr->logpen.elpWidth = abs(width); > + penPtr->logpen.elpWidth = width; > penPtr->logpen.elpBrushStyle = logbrush.lbStyle; > penPtr->logpen.elpColor = logbrush.lbColor; > penPtr->logpen.elpHatch = brush->lbHatch; This breaks a test: ../../../tools/runtest -q -P wine -T ../../.. -M gdi32.dll -p gdi32_test.exe.so pen && touch pen.ok pen.c:440: Test failed: expected 123, got ffffff85 width is actually treated as signed. Huw.

1 0

Re: [PATCH] advapi32, ntdll: Skip test_redirection tests if there is not enough privileges
by Marvin Feb. 17, 2016

Feb. 17, 2016

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=20601 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH] advapi32, ntdll: Skip test_redirection tests if there is not enough privileges
by Marvin Feb. 17, 2016

Feb. 17, 2016

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=20600 Your paranoid android. === build (build) === Patch failed to apply

1 0

[GSoC Things] Want to make wpcap.dll become more usable on wine
by Jianqiu Zhang Feb. 17, 2016

Feb. 17, 2016

Hi, I am working on improving and implementing more functions for wpcap.dll on wine wpcap is the Windows version of pcap, Packet Capture Library for wireshark and other network analyzing software, I have done some research on it, In wine we cannot use the windows kernel driver, but winpcap actually use it, so I follow the wine wpcap code and try to add more wrapper to wpcap, Here is the patch I' ve submitted and was add to wine-staging, https://github.com/wine-compholio/wine-staging/tree/master/patches/wpcap-Se… One of the most difficult point is , there aren't many applications using wpcap.dll, I cannot found plenty of them, According to fracting(Hong Qian) 's suggestions, Dr.com , a Client for many Chinese university students to gain access to cernet uses wpcap, If wpcap.dll can improved to make it available for Dr.Com , maybe many university students using Linux can gain access to cernet. I will try to improve wpcap.dll in two different ways: 1. Use wine wpcap.dll , and write wrappers 2. Write packet.dll which is needed by native wpcap.dll, and then use native wpcap.dll I will write testcase for the new dll packet.dll. Is there andy sugesstions on this idea? Any suggesstions are appreciated Thanks Jianqiu

3 3

Re: [PATCH] usp10/tests: Use todo_wine_if() in tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20594 Your paranoid android. === w1064 (32 bit usp10) === usp10.c:1423: Test failed: 0: uJustification incorrect (0) usp10.c:1423: Test failed: 1: uJustification incorrect (0) usp10.c:1423: Test failed: 2: uJustification incorrect (0) usp10.c:1423: Test failed: 3: uJustification incorrect (0) usp10.c:1423: Test failed: 4: uJustification incorrect (0) usp10.c:1423: Test failed: 5: uJustification incorrect (0) usp10.c:1423: Test failed: 6: uJustification incorrect (0) usp10.c:1423: Test failed: 7: uJustification incorrect (0) usp10.c:1423: Test failed: 8: uJustification incorrect (0) usp10.c:1423: Test failed: 9: uJustification incorrect (0) usp10.c:1439: Test failed: 3: uJustification incorrect (0) usp10.c:1439: Test failed: 5: fDiacritic incorrect (1) usp10.c:1439: Test failed: 5: fZeroWidth incorrect (1) usp10.c:1439: Test failed: 15: fDiacritic incorrect (1) usp10.c:1439: Test failed: 15: fZeroWidth incorrect (1)

1 0

Re: [PATCH] wininet/tests: Use todo_wine_if() in tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20593 Your paranoid android. === w1064 (32 bit internet) === internet.c:1507: Test failed: Got 0, expected 1223 (12042) internet.c:1512: Test failed: Got 0, expected 1223 (12042) internet.c:1521: Test failed: Got 0, expected 1223 (12042) internet.c:1074: Test failed: expected ret == 0, got 87

1 0

Re: [PATCH] ws2_32/tests: Use todo_wine_if() in tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20591 Your paranoid android. === w7pro64 (32 bit sock) === sock.c:7731: Test failed: bytesReturned isn't supposed to be 1 sock.c:7777: Test failed: Waiting for timeout failed with 0 + errno 997

1 0

Re: [v2] d3d8/tests: Use todo_wine_if() in tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20589 Your paranoid android. === w1064 (32 bit device) === device.c:2725: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2730: Test failed: The focus window is active. device.c:2738: Test failed: Got unexpected hr 0x88760869. device.c:2742: Test failed: Got unexpect screen size 800x600. device.c:2757: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2766: Test failed: Got unexpect screen size 800x600. device.c:2779: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2787: Test failed: Got unexpect width 640. device.c:2788: Test failed: Got unexpect height 480.

1 0

Re: [v2] d3d9/tests: Use todo_wine_if() in tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20588 Your paranoid android. === w1064 (32 bit d3d9ex) === d3d9ex.c:2347: Test failed: Got unexpected hr 0, i=0. d3d9ex.c:2349: Test failed: Got unexpected hr 0, i=0. d3d9ex.c:2347: Test failed: Got unexpected hr 0, i=1. d3d9ex.c:2349: Test failed: Got unexpected hr 0, i=1.

1 0

Re: [PATCH 6/6] d3d11/tests: Test relative addressing in constant buffers.
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20572 Your paranoid android. === wvistau64 (32 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 74199C9F === w2008s64 (32 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 74179C9F === wvistau64 (64 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 0000000074AAFCBB === w2008s64 (64 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 0000000073DAFCBB

1 0

Re: [v4] shell32: fix two bugs in IQueryAssocations
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20568 Your paranoid android. === w2003std (32 bit assoc) === assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x0 assoc.c:174: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x0 assoc.c:178: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x80070483 assoc.c:183: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x80070483 assoc.c:184: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x80070483 assoc.c:185: Test failed:

2 1

Re: d3d9/tests: Use todo_wine_if() in tests
by Henri Verbeet Feb. 16, 2016

Feb. 16, 2016

On 16 February 2016 at 12:31, Frédéric Delanoy <frederic.delanoy(a)gmail.com> wrote: > Signed-off-by: Frédéric Delanoy <frederic.delanoy(a)gmail.com> > --- > dlls/d3d9/tests/device.c | 20 ++++---------------- > dlls/d3d9/tests/visual.c | 22 ++++------------------ > 2 files changed, 8 insertions(+), 34 deletions(-) > Why did you do this for some tests, but not others? (E.g. you modify test_window_style() for d3d9, but not for d3d9ex.)

2 1

Re: [PATCH 2/2] mscoree: Implement ICorRuntimeHost::CreateDomain{, Ex}(). (try 4)
by Vincent Povirk Feb. 16, 2016

Feb. 16, 2016

It doesn't seem to work. According to the test program, GetDefaultDomain and CreateDomain are returning the same IUnknown. :( Maybe we need to set the thread domain somehow in RuntimeHost_Invoke?

1 0

Re: ddraw/tests: Use todo_wine_if() in tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20563 Your paranoid android. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw1) === ddraw1.c:2209: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit d3d) === d3d.c:2329: Test failed: Unexpected destination texture level pixels; 2031 differences at 0 level d3d.c:2329: Test failed: Unexpected destination texture level pixels; 518 differences at 1 level d3d.c:2329: Test failed: Unexpected destination texture level pixels; 138 differences at 2 level d3d.c:2329: Test failed: Unexpected destination texture level pixels; 46 differences at 3 level d3d.c:2513: Test failed: Unexpected destination texture level pixels; 257 differences d3d.c:2660: Test failed: Unexpected destination texture level pixels; 256 differences at 2 level d3d.c:2660: Test failed: Unexpected destination texture level pixels; 64 differences at 3 level d3d.c:2660: Test failed: Unexpected destination texture level pixels; 16 differences at 4 level d3d.c:2660: Test failed: Unexpected destination texture level pixels; 4 differences at 5 level === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

1 0

XInput: Comments on core and further steps
by Juan Jose Gonzalez Feb. 16, 2016

Feb. 16, 2016

Hi, I just published a patch with my xinput core implementation. If anyone is interested in an evdev (linux) backend I could publish that too, but I guess it won't make it into wine due to the tendency towards the HID architecture. A rough overview on how it's supposed to be used can be read in the README file from the second patch. Let me know what you think. The next step would be to implement a backend that uses hid.dll. Using HID devices should be fairly straightforward. There are, however, two parts that I haven't figured out yet: - How can we find new devices? The current work for the HID architecture seems to have tackled the hotplugging problem. Can the XInput HID backend get notified when a new controller gets plugged in? Should it just poll for new devices using SetupDi functions or something similar? - How do we map a controller's buttons and axes to the corresponding XInput ones? This has to be done per controller model. My evdev backend has a lookup list that matches controllers to a certain mapping using some selection criteria (Name, Vendor ID, etc.). My idea was to load the mappings from the registry, but for this to be usable by regular users, a GUI would have to be implemented to create those registry entries. Any ideas are welcome. Juan

4 10

Re: [PATCH 2/2 v4] user32: Add more dialog creation message tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20560 Your paranoid android. === wvistau64 (32 bit msg) === msg.c:13904: Test failed: 10: WaitForSingleObject failed msg.c:13904: Test failed: 11: WaitForSingleObject failed === w1064 (32 bit msg) === msg.c:6290: Test failed: Update region shouldn't be empty msg.c:6524: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6526: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6296: Test failed: Regions are different msg.c:6296: Test failed: Regions are different msg.c:6296: Test failed: Regions are different

1 0

Re: [PATCH 6/8] wined3d: Remove fbo_entry->d3d_depth_stencil.
by Henri Verbeet Feb. 16, 2016

Feb. 16, 2016

On 14 February 2016 at 21:33, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote: > Instead of storing the format flags we could store the depth and stencil > attachments as separate objects in the key. However, I don't think it is > worth making the key bigger. The depth and stencil attachment will > always be the same object. Another option would be to merge it with the "attached" field in to a "flags" field.

1 0

Re: [PATCH 1/8] wined3d: Retrieve FBO attachments from GL in context_check_fbo_status.
by Henri Verbeet Feb. 16, 2016

Feb. 16, 2016

On 14 February 2016 at 21:33, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote: > + if (gl_info->supported[EXT_FRAMEBUFFER_MULTISAMPLE]) > + gl_info->fbo_ops.glGetRenderbufferParameteriv(GL_RENDERBUFFER, GL_RENDERBUFFER_SAMPLES, &samples); > + else > + samples = 1; I don't think this will do the right thing in core contexts, or if only ARB_framebuffer_object is supported. > + gl_info->fbo_ops.glGetRenderbufferParameteriv(GL_RENDERBUFFER, GL_RENDERBUFFER_INTERNAL_FORMAT, &fmt); > + FIXME("\t%s: renderbuffer %d, %dx%d, %d samples, format %x.\n", > + debug_fboattachment(attachment), name, width, height, samples, fmt); The '\t' is from the original code of course, but please just replace it with spaces. > + FIXME("\t%s: %s texture %d, %dx%d, format %x.\n", debug_fboattachment(attachment), > + tex_type_str, name, width, height, fmt); %#x for hexadecimal, please. > +#define FBOATTACHMENT_TO_STR(u) case u: return #u The existing functions are a bit of a mess in this regard, but I'd prefer "WINED3D_TO_STR" for new functions. > + FIXME("Unrecognied FBO status 0x%08x\n", attachment); > + return "unrecognized"; The FIXME has room for improvement. You could also consider doing something like "return wine_dbg_sprintf("unknown attachment %#x", attachment);"

1 0

Patch assignment notifications
by Alexandre Julliard Feb. 16, 2016

Feb. 16, 2016

Folks, I've now added automated email notifications for when you are assigned patches to review. I've tried to make it not too annoying for frequent reviewers, and hopefully easy to filter. Please let me know what you think. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 2/2 v3] user32: Add more dialog creation message tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20553 Your paranoid android. === w1064 (32 bit msg) === msg.c:6290: Test failed: Update region shouldn't be empty msg.c:6524: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6526: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6296: Test failed: Regions are different msg.c:6296: Test failed: Regions are different msg.c:6296: Test failed: Regions are different

1 0

Re: [PATCH 2/2 v2] user32: Add more dialog creation message tests
by Dmitry Timoshkov Feb. 16, 2016

Feb. 16, 2016

Hi Piotr, this test doesn't actually provide any proof for the 1/2 patch. I'd expect to see a test that checks also the messages sent/received by edit control. -- Dmitry.

2 1

Re: [PATCH 2/2 v2] user32: Add more dialog creation message tests
by Marvin Feb. 16, 2016

Feb. 16, 2016

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=20550 Your paranoid android. === w7u (32 bit msg) === msg.c:8799: Test failed: did not get expected count for minimum timeout (54 != ~100). === w1064 (32 bit msg) === msg.c:6290: Test failed: Update region shouldn't be empty msg.c:6524: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6526: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6296: Test failed: Regions are different msg.c:6296: Test failed: Regions are different msg.c:6296: Test failed: Regions are different

1 0