On Sat, May 10, 2008 at 12:46 AM, Roderick Colenbrander
<[EMAIL PROTECTED]> wrote:
>> On a whim, I tried the oldest SPEC OpenGL benchmark, SPECviewperf 6.
>>
>> SPECViewperf 6.1.2 lives here:
>> http://www.spec.org/gwpg/pastissues/Feb2_02/opc.static/opcview.htm
>> It's also downloadable from
>> ftp
On Montag 19 Mai 2008, Jeremy White wrote:
> > ntdll:info is a flaky test marked todo_wine that succeeds sometimes:
> > "info.c:822: Test succeeded inside todo block: Expected to read 0
> > bytes, got 0"
>
> Hardy seems to be the common variable for failures, and it seems as though
> an actual fai
Dan Kegel wrote:
> Thanks to everybody who responded to Jeremy's call
> to run winetest using the 'dotests' script at
>http://wiki.winehq.org/MakeTestFailures
>
> We now have 35 reports, and have some good data on
> which test failures are common. See the
> Most Common Failures section at the
Another week, another winetricks.
Changes since last week's annoucement:
- gnome users now see nice package descriptions
- mfc42 is now listed as a synonym for vcrun6
Online as always at
http://kegel.com/wine/winetricks
or
http://winezeug.googlecode.com
> ntdll:info is a flaky test marked todo_wine that succeeds sometimes:
> "info.c:822: Test succeeded inside todo block: Expected to read 0
> bytes, got 0"
Hardy seems to be the common variable for failures, and it seems as though
an actual failure reading from location 0x1234 is the trigger.
(The
Thanks to everybody who responded to Jeremy's call
to run winetest using the 'dotests' script at
http://wiki.winehq.org/MakeTestFailures
We now have 35 reports, and have some good data on
which test failures are common. See the
Most Common Failures section at the bottom.
Here's what it says ri
I have filled the form but got error 404 after clicking "Request Trial
CD".
Mikołaj Zalewski
Am Montag, den 19.05.2008, 20:41 +0900 schrieb Dmitry Timoshkov:
> "Michael Karcher" <[EMAIL PROTECTED]> wrote:
> > http://msdn.microsoft.com/en-us/library/ms683893(VS.85).aspx
> > says so. I will test Microsoft's native implementation when I get around
> > to.
> That's the description of 32-bit im
Am Montag, den 19.05.2008, 19:58 +0900 schrieb Dmitry Timoshkov:
> > +INT WINAPI StringFromGUID2_16(REFGUID id, LPSTR str, INT cmax)
> > +{
> > + char xguid[80];
> > + int len;
> > +
> > + if (WINE_StringFromCLSID( id, xguid ))
> > + return 0;
> > +
> > + len = strlen( xguid ) + 1;
Jeremy White <[EMAIL PROTECTED]> writes:
>> Alexandre has said in the past that test failures for an incorrectly
>> or incompletely built wine tree should result in test failures and I
>> agree with this.
>
> Yah; I think to some extent we need to wait for Alexandre to express
> an opinion on how,
"Steven Edwards" <[EMAIL PROTECTED]> writes:
> On Sun, May 18, 2008 at 10:02 PM, Dmitry Timoshkov
> <[EMAIL PROTECTED]> wrote:
>> Not everyone supposed to run the Wine tests, only those do who *really*
>> can comprehend the results and able to do something with them.
>
> NO. Everyone that builds W
"Michael Karcher" <[EMAIL PROTECTED]> wrote:
>> This is not an equivalent of the old implementation, is it really
>> supposed to fail if the buffer length is shorter than the guid?
>
> http://msdn.microsoft.com/en-us/library/ms683893(VS.85).aspx
> says so. I will test Microsoft's native implement
"Michael Karcher" <[EMAIL PROTECTED]> wrote:
> +INT WINAPI StringFromGUID2_16(REFGUID id, LPSTR str, INT cmax)
> +{
> + char xguid[80];
> + int len;
> +
> + if (WINE_StringFromCLSID( id, xguid ))
> + return 0;
> +
> + len = strlen( xguid ) + 1; /* The terminating zero counts */
>
"James Hawkins" <[EMAIL PROTECTED]> wrote:
> if(detailed_info->lpRootManifestPath)
> ok(!lstrcmpiW(detailed_info->lpRootManifestPath,
> exinfo->root_manifest_path),
> - "unexpected detailed_info->lpRootManifestPath\n");
> + "unexpected detailed_in
14 matches
Mail list logo
