Call for help with Wine 1.0 testing

jwhite · Post by **jwhite** » Thu May 15, 2008 12:48 pm

Hi Folks,

One key goal for Wine 1.0 is that all of its conformance
tests run successfully on nearly all systems. We would really like
your help in figuring out how close we are to that goal.

To that end, if you are comfortable with checking Wine out via git,
could you please visit this page:
http://wiki.winehq.org/MakeTestFailures
and follow the instructions there? (It's really simple; build current
git Wine, download + run a script).

And, if you're a Wine developer, since Alexandre is away and the code freeze
is on, why not look for one of those failures in your own make test results and see
if you can fix it?

Thanks!

Jeremy

Susan Cragin · Post by **Susan Cragin** » Thu May 15, 2008 4:27 pm

This isn't a response, really, just more advice.
You should always have fontforge and msttcorefonts installed.
Then the best and easiest way to get the rest is:
sudo apt-get build-dep wine wine-dev
There's really a lot of stuff you need, and I found I didn't have the half of it.
Susan

-----Original Message-----

From: gnivler <[email protected]>
Sent: May 15, 2008 5:19 PM
To: [email protected]
Subject: [Wine] Re: Call for help with Wine 1.0 testing

jwhite wrote:
To that end, if you are comfortable with checking Wine out via git,
could you please visit this page:
http://wiki.winehq.org/MakeTestFailures
and follow the instructions there? (It's really simple; build current
git Wine, download + run a script).
Trying to follow along with the guide and hit a non-fatal warning but I don't know it's significance for testing. I'm using Ubuntu 64bit, compiled Wine from source a few days ago (tarball iirc). I've tried 'apt-get build-dep wine' (lists 6 deps already installed and current) and manually tried adding the first few listed missing packages/libs.. libxcursor-dev, libxi-dev, all report as installed. Haven't proceeded much further yet. My system should have full opengl support, I've got the proprietary nvidia beta 173 drivers installed with compiz running smoothly. I've also played two directX games in wine previously with no graphical issues, maybe a bit of choppiness. Am I missing more libraries still? That was an issue with the last compile I did. Thanks for any info/advice.

Code:
config.status: executing dlls/wineps.drv/data commands
config.status: executing include/wine commands

configure: libxcursor development files not found, the Xcursor extension won't be supported.
configure: libxi development files not found, the Xinput extension won't be supported.
configure: XShm development files not found, X Shared Memory won't be supported.
configure: XShape development files not found, XShape won't be supported.
configure: libXxf86vm development files not found, XFree86 Vidmode won't be supported.
configure: libxrender development files not found, XRender won't be supported.
configure: libxrandr development files not found, XRandr won't be supported.
configure: libxinerama development files not found, multi-monitor setups won't be supported.
configure: libxcomposite development files not found, Xcomposite won't be supported.
configure: libGLU development files not found, GLU won't be supported.
configure: libxml2 development files not found, XML won't be supported.
configure: libxslt development files not found, xslt won't be supported.
configure: libhal development files not found, no dynamic device support.
configure: libsane development files not found, scanners won't be supported.
configure: libgphoto2 development files not found, digital cameras won't be supported.
configure: liblcms development files not found, Color Management won't be supported.
configure: libldap (OpenLDAP) development files not found, LDAP won't be supported.
configure: libcapi20 development files not found, ISDN won't be supported.
configure: libcups development files not found, CUPS won't be supported.
configure: fontconfig development files not found, fontconfig won't be supported.
configure: OpenSSL development files not found, SSL won't be supported.
configure: libjpeg development files not found, JPEG won't be supported.
configure: libpng development files not found, PNG won't be supported.

configure: WARNING: No OpenGL library found on this system.
OpenGL and Direct3D won't be supported.

configure: WARNING: FreeType development files not found.
Fonts will not be built. Dialog text may be invisible or unaligned.

configure: Finished. Do 'make depend && make' to compile Wine.

Susan Cragin · Post by **Susan Cragin** » Thu May 15, 2008 4:33 pm

oh, and don't forget
xdg-utils !!

So the whole command would be:
sudo apt-get install msttcorefonts fontforge xdg-utils
sudo apt-get build-dep wine wine-dev

Then try compiling from git.

-----Original Message-----

From: Susan Cragin <[email protected]>
Sent: May 15, 2008 5:27 PM
To: [email protected]
Subject: Re: [Wine] Re: Call for help with Wine 1.0 testing

This isn't a response, really, just more advice.
You should always have fontforge and msttcorefonts installed.
Then the best and easiest way to get the rest is:
sudo apt-get build-dep wine wine-dev
There's really a lot of stuff you need, and I found I didn't have the half of it.
Susan

-----Original Message-----
From: gnivler <[email protected]>
Sent: May 15, 2008 5:19 PM
To: [email protected]
Subject: [Wine] Re: Call for help with Wine 1.0 testing

jwhite wrote:
To that end, if you are comfortable with checking Wine out via git,
could you please visit this page:
http://wiki.winehq.org/MakeTestFailures
and follow the instructions there? (It's really simple; build current
git Wine, download + run a script).
Trying to follow along with the guide and hit a non-fatal warning but I don't know it's significance for testing. I'm using Ubuntu 64bit, compiled Wine from source a few days ago (tarball iirc). I've tried 'apt-get build-dep wine' (lists 6 deps already installed and current) and manually tried adding the first few listed missing packages/libs.. libxcursor-dev, libxi-dev, all report as installed. Haven't proceeded much further yet. My system should have full opengl support, I've got the proprietary nvidia beta 173 drivers installed with compiz running smoothly. I've also played two directX games in wine previously with no graphical issues, maybe a bit of choppiness. Am I missing more libraries still? That was an issue with the last compile I did. Thanks for any info/advice.

Code:
config.status: executing dlls/wineps.drv/data commands
config.status: executing include/wine commands

configure: libxcursor development files not found, the Xcursor extension won't be supported.
configure: libxi development files not found, the Xinput extension won't be supported.
configure: XShm development files not found, X Shared Memory won't be supported.
configure: XShape development files not found, XShape won't be supported.
configure: libXxf86vm development files not found, XFree86 Vidmode won't be supported.
configure: libxrender development files not found, XRender won't be supported.
configure: libxrandr development files not found, XRandr won't be supported.
configure: libxinerama development files not found, multi-monitor setups won't be supported.
configure: libxcomposite development files not found, Xcomposite won't be supported.
configure: libGLU development files not found, GLU won't be supported.
configure: libxml2 development files not found, XML won't be supported.
configure: libxslt development files not found, xslt won't be supported.
configure: libhal development files not found, no dynamic device support.
configure: libsane development files not found, scanners won't be supported.
configure: libgphoto2 development files not found, digital cameras won't be supported.
configure: liblcms development files not found, Color Management won't be supported.
configure: libldap (OpenLDAP) development files not found, LDAP won't be supported.
configure: libcapi20 development files not found, ISDN won't be supported.
configure: libcups development files not found, CUPS won't be supported.
configure: fontconfig development files not found, fontconfig won't be supported.
configure: OpenSSL development files not found, SSL won't be supported.
configure: libjpeg development files not found, JPEG won't be supported.
configure: libpng development files not found, PNG won't be supported.

configure: WARNING: No OpenGL library found on this system.
OpenGL and Direct3D won't be supported.

configure: WARNING: FreeType development files not found.
Fonts will not be built. Dialog text may be invisible or unaligned.

configure: Finished. Do 'make depend && make' to compile Wine.

Post by **DanKegel** » Thu May 15, 2008 4:41 pm

See also
http://wiki.winehq.org/Recommended_Packages

"The easiest way to set up an Ubuntu system is to use a shell script
that installs the neccessary packages:
* Hardy Heron (Ubuntu 8.04) http://kegel.com/wine/hardy.sh
* Gutsy Gibbon (Ubuntu 7.10) http://kegel.com/wine/gutsy.sh
* Feisty Fawn (Ubuntu 7.04) http://kegel.com/wine/feisty.sh"

gnivler · Post by **gnivler** » Thu May 15, 2008 4:59 pm

Thanks for the suggestions I'm sure I'll get it compiled now. Strangely I had everything required before, I think apt-get autoremove may have screwed this up, it listed a bunch of stuff I didn't recognize, and removed it. Figured if I didn't know what it was it would be better to go with defaults. I did try installing the 32bit version of Hardy first but there was some apic problem where it wouldn't boot without a noapic option, then I read multicore cpus communicate internally with apic and I've also got 4 gigs of physical memory. Figured I would need 64bit to maximize my hardware even though it is overkill for a linux desktop. In any event I think I was just confused having already done it, and needing to do it again now.

edit: it's working great, the main issue was the missing library links, forgot they were temporarily installed into my previous wine source copy. ps this thread is missing posts, perhaps as a result of those short lived database issues just recently?

Post by **DanKegel** » Thu May 15, 2008 5:41 pm

On Thu, May 15, 2008 at 10:47 AM, Jeremy White <[email protected]> wrote:

One key goal for Wine 1.0 is that all of its conformance
tests run successfully on nearly all systems. We would really like
your help in figuring out how close we are to that goal.

To that end, if you are comfortable with checking Wine out via git,
could you please visit this page:
http://wiki.winehq.org/MakeTestFailures

The results are pouring in at
http://test.winehq.org/data/2470b0b3160 ... group_Wine

Say, who maintains that web site? It'd be handy to have an option to
suppress rows that have neither crashes nor failures; right now you have
to scroll vertically a whole lot to see all the failures.
- Dan

jwhite · Post by **jwhite** » Thu May 15, 2008 6:53 pm

Say, who maintains that web site? It'd be handy to have an option to
suppress rows that have neither crashes nor failures; right now you have
to scroll vertically a whole lot to see all the failures.

I'm not sure. The source is in this git tree:

http://source.winehq.org/git/tools.git

Cheers,

Jeremy

Post by **DanKegel** » Fri May 16, 2008 12:34 am

On Thu, May 15, 2008 at 4:52 PM, Jeremy White <[email protected]> wrote:

Say, who maintains that web site? It'd be handy to have an option to
suppress rows that have neither crashes nor failures; right now you have
to scroll vertically a whole lot to see all the failures.
I'm not sure. The source is in this git tree:
http://source.winehq.org/git/tools.git

I wrote a postprocessor to do it. It's at http://kegel.com/wine/skipgood.pl.txt
An example of its output is at http://kegel.com/wine/failing.html
It really does make it easier to see all the failures.

Timeout · Post by **Timeout** » Fri May 16, 2008 1:57 am

Last Git is not compiling for me. I get the message:

/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: cannot find -lXext
collect2: ld returned 1 exit status
winegcc: gcc failed
make[2]: *** [winex11.drv.so] Fehler 2
make[2]: Leaving directory `/home/../wine-git/dlls/winex11.drv'
make[1]: *** [winex11.drv] Fehler 2
make[1]: Leaving directory `/home/../wine-git/dlls'
make: *** [dlls] Fehler 2

although I used ./configure --x-libraries=/usr/x11R6/lib && make
to compile and all X-org libraries (32 and 64 bit) are there

Usually it does compile fine

John Klehm · Post by **John Klehm** » Fri May 16, 2008 3:07 am

On Fri, May 16, 2008 at 12:33 AM, Dan Kegel <[email protected]> wrote:

On Thu, May 15, 2008 at 4:52 PM, Jeremy White <[email protected]> wrote:
I wrote a postprocessor to do it. It's at http://kegel.com/wine/skipgood.pl.txt
An example of its output is at http://kegel.com/wine/failing.html
It really does make it easier to see all the failures.

Your webserver doesn't like serving your skipgood.pl.txt file =/

--John

Reece Dunn · Post by **Reece Dunn** » Fri May 16, 2008 3:07 am

2008/5/16 Dan Kegel <[email protected]>:

On Thu, May 15, 2008 at 4:52 PM, Jeremy White <[email protected]> wrote:
Say, who maintains that web site? It'd be handy to have an option to
suppress rows that have neither crashes nor failures; right now you have
to scroll vertically a whole lot to see all the failures.
I'm not sure. The source is in this git tree:
http://source.winehq.org/git/tools.git
I wrote a postprocessor to do it. It's at http://kegel.com/wine/skipgood.pl.txt
An example of its output is at http://kegel.com/wine/failing.html
It really does make it easier to see all the failures.

Looks nice, but the original one is useful too as it shows the todo
and skipped results in there as well.

Is there a way to show how many tests are failing because they are
todo block successes. For example, the ntdll results can be ignored as
the error is a todo block success that seems to be triggered only on
certain machines (3/4 of the 17 results thus far); this would then
help focus the effort on the failures that are more important.

- Reece

Post by **DanKegel** » Fri May 16, 2008 9:59 am

On Thu, May 15, 2008 at 10:43 PM, John Klehm <[email protected]> wrote:

I wrote a postprocessor to do it. It's at http://kegel.com/wine/skipgood.pl.txt
An example of its output is at http://kegel.com/wine/failing.html
It really does make it easier to see all the failures.
Your webserver doesn't like serving your skipgood.pl.txt file =/

Bleah. I added a symlink, you can see it now at
http://kegel.com/wine/skipgood.txt

I also updated http://kegel.com/wine/failing.html
It's very interesting to see what's failing!

The d3d9/visual tests seemed to pass for Jeremy White, but only because
a skip() was missing. Patch sent,
http://winehq.org/pipermail/wine-patche ... 54930.html

The only tests that are failing for every system are shell32:shelllink
and d3d9/visual.
shelllink doesn't fail when run via make test,
so it might be a winetest artifact.

Do the d3d9/visual tests really pass for *anybody*?

The user32/msg tests pass if you have a good window manager, as noted
on http://wiki.winehq.org/MakeTestFailures

As Jeremy suggested, several of the remaining failures might
be missing packages at build time, and we could deal with some
of those by making them mandatory.
- Dan

Post by **DanKegel** » Fri May 16, 2008 10:01 am

On Fri, May 16, 2008 at 12:37 AM, Reece Dunn <[email protected]> wrote:

I wrote a postprocessor to do it. It's at http://kegel.com/wine/skipgood.pl.txt
An example of its output is at http://kegel.com/wine/failing.html
Looks nice, but the original one is useful too as it shows the todo
and skipped results in there as well.

Yeah. How 'bout this: provide both the original and the postprocessed
file. People who want the postprocessed version will just have to
know to add /failing.html for now. That will get us up and running quick.

Is there a way to show how many tests are failing because they are
todo block successes. For example, the ntdll results can be ignored as
the error is a todo block success that seems to be triggered only on
certain machines (3/4 of the 17 results thus far); this would then
help focus the effort on the failures that are more important.

Not easy for the postprocessor given the current data, I think.
I wouldn't worry about that detail too much.

austin987 · Post by **austin987** » Fri May 16, 2008 4:58 pm

On Thu, May 15, 2008 at 12:47 PM, Jeremy White <[email protected]> wrote:

Hi Folks,

One key goal for Wine 1.0 is that all of its conformance
tests run successfully on nearly all systems. We would really like
your help in figuring out how close we are to that goal.

To that end, if you are comfortable with checking Wine out via git,
could you please visit this page:
http://wiki.winehq.org/MakeTestFailures
and follow the instructions there? (It's really simple; build current
git Wine, download + run a script).

And, if you're a Wine developer, since Alexandre is away and the code freeze
is on, why not look for one of those failures in your own make test results
and see
if you can fix it?

Thanks!

Jeremy

I've updated http://wiki.winehq.org/MakeTestFailures a bit. I've added
more bug reports for test failures, and split them into generic and
specific bug reports.

@wine-devel:
I've tagged quite a few bugs that only occur on PC-BSD and/or
OpenSolaris, but not in Ubuntu Feisty (on a vm with the same
settings). Anyone with spare time might take a look at those bugs, and
see what is blocking our porting efforts. I'll work on getting those
two on real hardware sometime in the next week or two for better
testing.

@wine-users
Try testing this under as much hardware as you can. Just make sure
wine is compiling properly (check ./configure --verbose for any
warnings).

-Austin