August 2007 - Wine-Devel - list.winehq.org

Re: A script for automatic regression testing

by Jakob Eriksson

Completely awesome, thank you! Mikolaj Zalewski wrote: > I wrote a small script that automates regression testing. It requires > an Autohotkey script that tests the program and creates a file > C:\Test-failed.txt if the test failed. The bash script will then do > the regression testing. It starts with copying the source tree and > wineprefix so it should be possible to do some normal work during > compilations. > At the beginning of the script there are some variables that needs to > be configured before running it. The wineprefix has to have Autohotkey > installed and associated with *.ahk. The attached script's settings > will find the regression for bug #9249. > If anyone is interested in it I'd be interested in some feedback. > > Mikołaj Zalewski > ------------------------------------------------------------------------ > > >

Aug. 13, 2007

Re: win16 tests

by Jakob Eriksson

It would be sweet if you put up the executables too. Jennifer Lai wrote: > Hi, > > I've collected and fixed some win16 tests. > Since they are not going to be included in the wine tree, I've placed them under > http://www.cs.ucla.edu/~jlai/win16test/ > In order to build these tests, Open Watcom was used. The tar ball also > includes the scripts of installing Open Watcom, building the tests, > and running them. Details are described in the README. > More tests will be added in the future, and comments are greatly appreciated. > > Thank you, > Jennifer Lai > >

Aug. 13, 2007

Re: Allow building of ddraw.dll / ddrawex.dll on MingW

by Alexandre Julliard

Stefan Dösinger <stefan(a)codeweavers.com> writes: > I don't think mingw's dxguid is outdated. IDirectDraw3 is an internet-explorer > internal interface, so I don't think any windows library exports that GUID > publically. I am not sure how to deal with it. If it's not in the Windows libdxguid it shouldn't be in the Wine one. The GUID can be declared in the C files that need it. -- Alexandre Julliard julliard(a)winehq.org

Aug. 13, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Paul Vriens

Detlef Riekenberg wrote: > On Fr, 2007-08-10 at 12:15 +0200, Paul Vriens wrote: >> I just want to get people's opinion(s) about the needs/requirements/whishes for >> both the conformance tests themselves (including winetest) as well as the webpages. > Hi Detlef > * Please make the links "Previous build" / "Next build" working! This has been bothering me for ages. I only ever looked briefly into this, but either the links should be correct or be removed. > > * I really like to Filter the Results by DLL: What do you mean by filter? Currently the results are 'filtered' by test. Would you like a page just for your DLL? > - Try to find the Test-Result, when a new Failure popped up > in a specific Windows Version. > (Current Example is oleauth32/vartest for w2k) 'New failure' = 'different result than the previous run' ? > > - Try to find the most recently Results for a Test. > (For Example, when a new Test was added) > Find this for a specific Windows Version. The most recent results are in the last run. Or do you mean something else. I would like to have a 'latest' link on test.winehq.org/data as a very simple way of getting to the last version run. > > * http://bugs.winehq.org/show_bug.cgi?id=3187 > > > * Can we add the selected locale to the results? > (Example issue are the current failures in oleauth32/vartest) Do you want this in the report (text) or on the html page? > > > * Can we add the tested dll-version to the results? > (This is a shortcut for the installed versions of: > IE, msi, DirectX, ...) Again in the report or on the page? And only for the main dll (main dll equals the root directory of the test)? For msi that would be msi.dll, for the other 2 you mention it will be more difficult as they are comprised of several dll's. So how would like to see that? > > * winetest.exe: Allow "/?" as an alias for "-h" > * winetest.exe: Allow other character in the TAG (underscore as example) > * winetest.exe: Enable the "Stop" button > * winetest.exe: make the progress-bars the same size > * winetest.exe: Be more verbose during extract / test / upload > (add "x of y" somewhere; add used time somewhere) > > Can we optional collect the results with a tempfile to replace the Pipe? > (set WINETEST_OUTPUT to the Filename as Example) > > This will make it possible with an updated wine/test.h to add win16 > tests in the testsuite. > > I do not expect to run winetest on win3.x, but just prevent the 16Bit > API to fail. > > These last ones I only glanced at, but will look deeper soon. From the first items in you list it looks you'd like some sort of search/input page that generator output. Is that correct? Cheers, Paul.

Aug. 13, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Paul Vriens

Stefan Leichter wrote: > Am Friday 10 August 2007 12:15 schrieb Paul Vriens: >> Hi, >> >> I just want to get people's opinion(s) about the needs/requirements/whishes >> for both the conformance tests themselves (including winetest) as well as >> the webpages. >> >> I'll collect the information and will put it on the wiki. >> >> Cheers, >> >> Paul. > > What about marking the "todo_wine" on the web page somehow? > > Bye Stefan > > Hi Stefan, todo_wine will only be present on a Wine testrun. Results for each test are available (including todo) when you hover over the single results. We can of course use a general 'todo' visualization but who do you like to see that? Or was you're idea to show todo_wine's in Windows results !? Cheers, Paul.

Aug. 13, 2007

Re: Allow building of ddraw.dll / ddrawex.dll on MingW

by Stefan Dösinger

Am Sonntag, 12. August 2007 22:09 schrieb Roderick Colenbrander: > Hi, > > I think I got my mingw from the debian packages. Others also suggested that > the dxguid version in mingw was outdated. I don't think mingw's dxguid is outdated. IDirectDraw3 is an internet-explorer internal interface, so I don't think any windows library exports that GUID publically. I am not sure how to deal with it.

Aug. 13, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Detlef Riekenberg

On Fr, 2007-08-10 at 12:15 +0200, Paul Vriens wrote: > I just want to get people's opinion(s) about the needs/requirements/whishes for > both the conformance tests themselves (including winetest) as well as the webpages. * Please make the links "Previous build" / "Next build" working! * I really like to Filter the Results by DLL: - Try to find the Test-Result, when a new Failure popped up in a specific Windows Version. (Current Example is oleauth32/vartest for w2k) - Try to find the most recently Results for a Test. (For Example, when a new Test was added) Find this for a specific Windows Version. * http://bugs.winehq.org/show_bug.cgi?id=3187 * Can we add the selected locale to the results? (Example issue are the current failures in oleauth32/vartest) * Can we add the tested dll-version to the results? (This is a shortcut for the installed versions of: IE, msi, DirectX, ...) * winetest.exe: Allow "/?" as an alias for "-h" * winetest.exe: Allow other character in the TAG (underscore as example) * winetest.exe: Enable the "Stop" button * winetest.exe: make the progress-bars the same size * winetest.exe: Be more verbose during extract / test / upload (add "x of y" somewhere; add used time somewhere) Can we optional collect the results with a tempfile to replace the Pipe? (set WINETEST_OUTPUT to the Filename as Example) This will make it possible with an updated wine/test.h to add win16 tests in the testsuite. I do not expect to run winetest on win3.x, but just prevent the 16Bit API to fail. -- By by ... Detlef

Aug. 13, 2007

Re: Fonts (+liberation again...)

by Alexandre Julliard

"Louis. Lenders" <xerox_xerox2000(a)yahoo.co.uk> writes: > Of course this patch lacks checking for presence of liberation, and > has ugly hard-coded path for the liberation-font, but that could be > worked on later on. > > Simple question: Could something like this be included in the > source, otherwise i'm not gonna spend any time improving it. Any > hints welcomed. No, it can't be included, the fonts are GPL not LGPL, and you don't want to silently insert them into the Wine binary packages. -- Alexandre Julliard julliard(a)winehq.org

Aug. 13, 2007

Re: [oleaut32/tests] Error when running tests on Wine, anyone?

by Paul Vriens

Detlef Riekenberg wrote: > On So, 2007-08-12 at 10:50 +0200, Stefan Leichter wrote: >>>> Can somebody confirm if all oleaut32 tests run correctly on Wine. >>> detlef(a)p4:~/wine.cvs/bin$ wine dlls/oleaut32/tests/oleaut32_test.exe.so >>> vartest > ... >>> vartest.c:3129: Test failed: got VT_R8(-145) expected VT_R8(-1.4) >>> vartest: 1031878 tests executed (0 marked as todo, 1 failure), 0 >>> skipped. >>> Intel P4 2GHz / Ubuntu 6.06 >> Should we think about localisation? > > That's the reason for the failure! > LANG="en_GB.UTF-8" wine ... => 0 failures > Also for "en_GB", "it_IT", "fr_FR", "gr_GR", .... > >> Of course we are running both debian base distributions. This might be another >> item to look on. > > Not needed. > Our tests are not correct for w2k and below. > My w2k_sp4(german) has 539 failures and includes the failure from wine: >> vartest.c:3129: Test failed: got VT_R8(-145) expected VT_R8(-1.4) > > > The WRT-Resultpage has 536 failures for w2k: > http://test.winehq.org/data/200708071000/2000_W2KProf-Admin/oleaut32:vartes… > > > OK, we have a few results now and it we know that localization is important. This however doesn't fix it for me, so there are more variables. I'm running on FC7 x86_64 with gcc 4.1.2. If people can post there versions etc.. we can maybe come up with the other variables (this also means people where the tests succeeds). So far: - localization influences the tests (which make sense because of the '.' in 1.45 which is a ',' in other locales) - I have 2 failures reported (with the same results) on a FC6/FC7 x86_64. So maybe the 64-bit is a variable as well. Cheers, Paul.

Aug. 13, 2007

Re: [oleaut32/tests] Error when running tests on Wine, anyone?

by Detlef Riekenberg

On So, 2007-08-12 at 10:50 +0200, Stefan Leichter wrote: > > > Can somebody confirm if all oleaut32 tests run correctly on Wine. > > > > detlef(a)p4:~/wine.cvs/bin$ wine dlls/oleaut32/tests/oleaut32_test.exe.so > > vartest ... > > vartest.c:3129: Test failed: got VT_R8(-145) expected VT_R8(-1.4) > > vartest: 1031878 tests executed (0 marked as todo, 1 failure), 0 > > skipped. > > Intel P4 2GHz / Ubuntu 6.06 > > Should we think about localisation? That's the reason for the failure! LANG="en_GB.UTF-8" wine ... => 0 failures Also for "en_GB", "it_IT", "fr_FR", "gr_GR", .... > Of course we are running both debian base distributions. This might be another > item to look on. Not needed. Our tests are not correct for w2k and below. My w2k_sp4(german) has 539 failures and includes the failure from wine: > vartest.c:3129: Test failed: got VT_R8(-145) expected VT_R8(-1.4) The WRT-Resultpage has 536 failures for w2k: http://test.winehq.org/data/200708071000/2000_W2KProf-Admin/oleaut32:vartes… -- By by ... Detlef

Aug. 13, 2007