wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Winetest publishers
by Dimitrie O. Paun 22 Apr '04

22 Apr '04

Hi Brian, A few more thoughts on the multiple publisher idea, and what we need to do on the server side. So, let's assume we have a number publishers out there. On server side we need to: 1. Maintain a pool of published winetest.exe's 2. Implement policy to serve from that pool (on a poll even) 1. The pool The pool will have to be maintained in a persistent manner to survive server reboots. It needs to get saved in a file. It should be managed as such: When a publish event happen we do: - check that the publisher id exists in publishers.txt file (1) - reject the event if not - check that it's really the publisher who publishes (2) - reject if not - check that the new BUILD_ID is >= than the current BUILD_ID - reject if not - if greater, reset the pool - add the published test to the pool - return 'OK' NOTES: (1) I suggest this format for publishers.txt <publisher-id>:<publisher-base-url> (2) We need to check that someone doesn't want to polute the pool. I suggest checking for the existance of: <publisher-base-url>/<published-file> 2. The Policy The sky's the limit. For now, we can just pick one at random from the pool. -- Dimi.

2 1

Invalid curdrive and curdir
by jeffl 22 Apr '04

22 Apr '04

All, I am tracking a problem where an install program with an exception trying to access 0x00000000 memory. I have tracked the problem down to files/drive.c in DRIVE_GetCurrentDirectory where dos_cwd contains 0 and is used in ret = strlenW(dos_cwd) + 3; /* length of WHOLE current directory */ It seems that DRIVE_GetCurrentDrive returns a value greater than MAX_DOS_DRIVES (25) and then return DOSDrives[drive].dos_cwd; where dos_cwd=0; pTask->curdrive and pTask->curdir appear not to be set or invalid. Now it seems that a check for null ptr in DRIVE_GetCurrentDirectory is order ie. UINT ret; LPCWSTR dos_cwd = DRIVE_GetDosCwd( DRIVE_GetCurrentDrive() ); static const WCHAR driveA_rootW[] = {'A',':','\\',0}; if (dos_cwd == 0) { ERR("dos_cwd returned 0 instead of pointer to current working directory\n"); dos_cwd = "\0"; /* make a valid string for strlenW */ } ret = strlenW(dos_cwd) + 3; /* length of WHOLE current directory */ if (ret >= buflen) return ret + 1; but what would be a good value for dos_cwd? I am interested in what causes the pTask->curdrive to be greater than 25 and curdir to be set to ???????? as shown below. Wine-dbg>p *pTask {hNext=0, ss_sp=0, nEvents=0, priority=0, unused1=0, hSelf=4143, hPrevInstance=0, unused2=0, ctrlword8087=0, flags=16, error_mode=0, version=1024, hInstance=0, hModule=0, hQueue=4199, hParent=0, signal_flags=0, sighandler=0x00000000, userhandler=0x00000000, discardhandler=0x00000000, int0=0x00000000, int2=0x00000000, int4=0x00000000, int6=0x00000000, int7=0x00000000, int3e=0x00000000, int75=0x00000000, compat_flags=0, unused4="", teb=0x4002f000, unused5="", hPDB=4151, dta=272040064, curdrive=254, curdir="????????", nCmdShow=1, hYieldTo=0, dlls_to_init=0, hCSAlias=4167, thunks={0, 21584, 0, 8, 16, 0, 0, 0, 24, 0, 0, 0, 32, 0, 0, 0, 40, 0, 0, 0, 48, 0, 0, 0, 56, 0, 0, 0, 0, 0, 0, 0}, module_name="", magic=17492, hEvent=0x0000000c, pdb={int20=8397, nextParagraph=0, reserved1=0, dispatcher="?", savedint22=0x00000000, savedint23=0x00000000, savedint24=0x00000000, parentPSP=0, fileHandles="????????????????????", environment=4159, saveStack=0, nbFiles=20, fileHandlesPtr=272039960, hFileHandles=0, reserved3={0, 0, 0, ...}, ...}...} Wine-dbg> Jeff Latimer

1 0

Anyone working on WSALookupServiceBegin() and WSALookupServiceNext?
by Robbert Xerox 22 Apr '04

22 Apr '04

Simple question : is anyone working on WSALookupServiceBegin() and WSALookupServiceNext() in winsock? ____________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

1 0

richedit - anybody trying to do it ?
by Krzysztof Foltman 22 Apr '04

22 Apr '04

Hi, Just out of curiosity: is anyone already actively developing a (supposedly) fully featured richedit control ? The current version looks like a plain editor combined with RTF reader... -- Chris

5 5

speed up oleaut32: vartest
by Chris Morgan 22 Apr '04

22 Apr '04

*dlls/oleaut32/tests/vartest.c: Chris Morgan<cmorgan(a)alum.wpi.edu> Skip over most of the unused variant types to speed up the variant tests. This look like a reasonable way to speed up the variant tests without losing testing functionality? Chris

1 1

RE: Fix for GetFileTime API - Incorrect Modified/Last access Time .
by Krishna Murthy 22 Apr '04

22 Apr '04

We have Team Developer Product for MS Windows which has its own language and in the process of verifying on Wine. Few of test cases working on Windows are failing in Wine. Hence I have submitted this patch. Yes, since Pre-1970 times are not going to work on Unix anyway we could release note this in our product. Thanks for your input on this. Krishna -----Original Message----- From: Alexandre Julliard [mailto:julliard@winehq.org] Sent: Wednesday, April 21, 2004 6:16 PM To: Krishna Murthy Cc: wine-devel(a)winehq.org Subject: Re: Fix for GetFileTime API - Incorrect Modified/Last access Time. Krishna Murthy <Krishna.Murthy(a)guptaworldwide.com> writes: > Change of argument type DWORD to LONGLONG of function > RtlSecondsSince1970ToTime() and RtlSecondsSince1980ToTime() to accept > negative values. These are Windows APIs, you cannot simply change their arguments, we have to be compatible. Pre-1970 times are not going to work right on Unix anyway; what do you need them for? -- Alexandre Julliard julliard(a)winehq.org

1 0

winetest oddity - oleaut32: VarTest
by Chris Morgan 22 Apr '04

22 Apr '04

I've been looking at vartest, specifically to speed it up since the tests I added for VarMod() are the cause of its current excessive length. Something appears to be a bit different with mingw compiled tests vs. MSVC compiled tests. Under wine these tests run just fine, three fixmes popup. I get two failures when running the oleaut32 vartest on my XP machine. This is compiled with vc6sp5+processor pack. Running the mingw compiled test from Paul Millar, http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/winetest-20040421-100…, there are thousands of failures for the same test. Anyone have a clue what might be causing this? One thing that came to mind was that there are int64's used in the ole code, the test won't compile cleanly under vc6 without the processor pack. Maybe mingw is messing up the int64's? Chris

1 0

Re: Fix for GetFileTime API - Incorrect Modified/Last access Time.
by Alexandre Julliard 22 Apr '04

22 Apr '04

Krishna Murthy <Krishna.Murthy(a)guptaworldwide.com> writes: > Change of argument type DWORD to LONGLONG of function > RtlSecondsSince1970ToTime() and RtlSecondsSince1980ToTime() to accept > negative values. These are Windows APIs, you cannot simply change their arguments, we have to be compatible. Pre-1970 times are not going to work right on Unix anyway; what do you need them for? -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Wine detect patch (ignore previous whitespace patch)
by Ferenc Wagner 21 Apr '04

21 Apr '04

Jakob Eriksson <jakov(a)vmlinux.org> writes: > (Sorry about the linespace noise after print_version(), > emacs seems to change stuff behind my back when I save.) Hi Jakob, You'd better educate Emacs about your ways, otherwise all your patches will be full of whitespace changes making them very hard to review. The indentation isn't consistent, but if you want to fix this, do so in a separate patch, please! > + static const TCHAR wine[128] = {"Wine"}; I think we could use static const char wine[] = "Wine"; instead. No wide characters in winetest for now. But see below! > + if (running_on_wine ()) { /* Make a an obvious signature for Wine */ > + ext = 1; > + > + ver.dwMajorVersion = 1; > + ver.dwMinorVersion = 1; > + ver.dwBuildNumber = 1; > + ver.dwPlatformId = 1; > + strncpy (ver.szCSDVersion, wine, sizeof (wine)); > + } > + I think we can do better. A single line like xprintf (" bRunningUnderWine=%d\n", running_under_wine ()); as the first line of print_version() would do a perfect job without masking anything else. -- Feri.

2 1

Re: Winetest results uploaded... where?
by Ivan Leo Murray-Smith 21 Apr '04

21 Apr '04

On http://test.winehq.org/data/200404192305/ the "next build" and "previous build" buttons are broken. I get a error message, saying "You don't have permission to access /site on this server." Ivan.

4 12

Re: White-space patch for programs/winetest/main.c
by Alexandre Julliard 21 Apr '04

21 Apr '04

Jakob Eriksson <jakov(a)vmlinux.org> writes: > This is also an example of how the file can store its indent > preference in a comment. > > I will run this when I'm done editing the file: > FILENAME=main.c && `grep indent $FILENAME` $FILENAME I don't think that's a good idea at all. It would require everybody to do that every time they make a change to that file, otherwise there will be plenty of spurious whitespace changes and conflicts. Please don't do that. -- Alexandre Julliard julliard(a)winehq.org

2 2

i810 audio fixes 1/2
by Roderick Colenbrander 21 Apr '04

21 Apr '04

Hi, This is the first of two patches that will fix some problems on soundcards using the i810 audio codec. The main probem with this soundcard is that it only supports a frequency of 48kHz in 16bit stereo mode. This first patch to dsound queries if the card supports 16bit and if so it uses it, else it uses 8bit. Further it also detects if the card supports stereo or not. The patch was inspired by one from transgaming to rewind but that patch did a bit the opposite (defaulting to 8bit ..). Roderick Colenbrander

8 18

Re: Widl: Conditionals, Dotted Versions, Handles
by Robert Shearman 21 Apr '04

21 Apr '04

>>> Ove Kaaven <ovek(a)arcticnet.no> 04/19/04 22:50 PM >>> man, 19.04.2004 kl. 17.03 skrev Robert Shearman: > > > Doesn't the "version" rule already handle this? > > > > It would appear not. The 'version' type is declared > as a number further up > > It's declared that the rule *returns* a number, you mean. The actual > rule is defined as > > version: > aNUM { $$ = MAKELONG($1, 0); } > | aNUM '.' aNUM { $$ = MAKELONG($1, $3); } > ; > > Now if this somehow returns 0, then you need to fix that rule, not add > another rule which makes a version of e.g. "1.2.3.4" valid syntax (but > still return a wrong result). Ok, I missed that before. I suspect it doesn't work properly because it correctly matches aNUM and attempts to convert it to a number and succeeds (but returning 0). We should re-arrange that rule so that the dotted version matches first and falls back to the second version if there is no '.'. However, I doubt I will have the time to resend that patch for a while. Rob

1 0

winetest reporting http://test.winehq.org/data/200404192305/
by Jakob Eriksson 21 Apr '04

21 Apr '04

First of all, the report on http://test.winehq.org/data/200404192305/ is VERY pretty. Almost get misty eyed here. ;-) Things are coming along very nicely. Anyway, I am curious what happens if I run winetest.exe in Wine. Will it get reported accurately as Wine, or will it get misrepresented in for instance the XP column? regards, Jakob

4 7

Serial and pread
by Izak Burger 21 Apr '04

21 Apr '04

Hello, I'm currently debugging a problem with serial comms over wine, and I see that when a serial device is opened (in server/serial.c) the serial_get_info function returns a type of FD_TYPE_DEFAULT, which in turn causes the serial device to be read from and written to with pread and pwrite in dlls/ntdll/file.c. Will this even work? I mean, how can you write or read to a serial port while using an offset? In any case, I changed the code to return FD_TYPE_SOCKET instead ( I thought a serial port is probably a lot more like a socket than it is a file) and now I get some activity on the serial port (before there was nothing), but it still does not work as it should. Not to worry, I just wanted to ask if all the trouble people were having with async serial comms might not be related to this? Any ideas greatly appreciated. regards, Izak

3 7

20040408 on freebsd4.9
by eternal 21 Apr '04

21 Apr '04

hello all... been stumped on this one for about a week now... been on the wine-users list trying to get this worked out, and mr. pfeifer was even nice enough to lend some advice that yeilded some build progress, but it (wine) seems to hate the idea of running on my puter... here's the info...: tyan tiger 100 dual p3-850 512MB ECC ati radeon 8500LE FreeBSD4.9-RELEASE and below is the output from env (initial login as vertigo, startx, open console, su root, env): USER=vertigo MAIL=/var/mail/vertigo OLDPWD=/home/vertigo HOME=/root GTK_RC_FILES=/usr/X11R6/etc/gtk/gtkrc:/home/vertigo/.gtkrc-1.2-gnome2 PAGER=more ENV=/home/vertigo/.shrc COLORTERM=gnome-terminal LOGNAME=vertigo WINDOWID=25165870 TERM=xterm BLOCKSIZE=K GNOME_DESKTOP_SESSION_ID=Default SESSION_MANAGER=local/eTernaL.null.org:/tmp/.ICE-unix/620 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin DISPLAY=:0.0 DESKTOP_STARTUP_ID= XAUTHORITY=/home/vertigo/.Xauthority SHELL=/bin/csh PWD=/home/vertigo/winecvs EDITOR=vi HOSTTYPE=FreeBSD VENDOR=intel OSTYPE=FreeBSD MACHTYPE=i386 SHLVL=1 GROUP=wheel CC=/usr/local/bin/gcc33 LD_LIBRARY_PATH=/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.3.1 first off, i get all the recent wine packages from cvs, i save it at /home/vertigo/winecvs, and again at /home/vertigo/winebackup. cd winecvs as vertigo, ./tools/wineinstall returns "not found". ls -la tools shows that is there... su root, check env (hence it's inclusion above), ./configure && make depend run fine. from past experience, i do the following make > winemake.txt after about 2700 lines of output, make stops with: rm -f winepath && ln -s ../../tools/winewrapper winepath /usr/local/bin/gcc33 -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o gui.o gui.c /usr/local/bin/gcc33 -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o main.o main.c /usr/local/bin/gcc33 -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o send.o send.c /usr/local/bin/gcc33 -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o util.o util.c ../../tools/winebuild/winebuild -o winetest.exe.dbg.c --debug -C. gui.c main.c send.c util.c /usr/local/bin/gcc33 -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o winetest.exe.dbg.o winetest.exe.dbg.c ../../tools/bin2res -f -o wine.ico ./gui.rc ./maketest ../.. advapi32_test.exe$(DLLEXT) comctl32_test.exe$(DLLEXT) gdi32_test.exe$(DLLEXT) kernel32_test.exe$(DLLEXT) msvcrt_test.exe$(DLLEXT) netapi32_test.exe$(DLLEXT) ntdll_test.exe$(DLLEXT) oleaut32_test.exe$(DLLEXT) rpcrt4_test.exe$(DLLEXT) shell32_test.exe$(DLLEXT) shlwapi_test.exe$(DLLEXT) urlmon_test.exe$(DLLEXT) user32_test.exe$(DLLEXT) wininet_test.exe$(DLLEXT) winmm_test.exe$(DLLEXT) winspool.drv_test.exe$(DLLEXT) ws2_32_test.exe$(DLLEXT) > winetest.rc || ( rm -f winetest.rc && exit 1 ) cp ../../dlls/advapi32/tests/advapi32_test.exe.so advapi32_test.exe.so && strip advapi32_test.exe.so cp ../../dlls/comctl32/tests/comctl32_test.exe.so comctl32_test.exe.so && strip comctl32_test.exe.so cp ../../dlls/gdi/tests/gdi32_test.exe.so gdi32_test.exe.so && strip gdi32_test.exe.so cp ../../dlls/kernel/tests/kernel32_test.exe.so kernel32_test.exe.so && strip kernel32_test.exe.so cp ../../dlls/msvcrt/tests/msvcrt_test.exe.so msvcrt_test.exe.so && strip msvcrt_test.exe.so cp ../../dlls/netapi32/tests/netapi32_test.exe.so netapi32_test.exe.so && strip netapi32_test.exe.so cp ../../dlls/ntdll/tests/ntdll_test.exe.so ntdll_test.exe.so && strip ntdll_test.exe.so cp ../../dlls/oleaut32/tests/oleaut32_test.exe.so oleaut32_test.exe.so && strip oleaut32_test.exe.so cp ../../dlls/rpcrt4/tests/rpcrt4_test.exe.so rpcrt4_test.exe.so && strip rpcrt4_test.exe.so cp ../../dlls/shell32/tests/shell32_test.exe.so shell32_test.exe.so && strip shell32_test.exe.so cp ../../dlls/shlwapi/tests/shlwapi_test.exe.so shlwapi_test.exe.so && strip shlwapi_test.exe.so cp ../../dlls/urlmon/tests/urlmon_test.exe.so urlmon_test.exe.so && strip urlmon_test.exe.so cp ../../dlls/user/tests/user32_test.exe.so user32_test.exe.so && strip user32_test.exe.so cp ../../dlls/wininet/tests/wininet_test.exe.so wininet_test.exe.so && strip wininet_test.exe.so cp ../../dlls/winmm/tests/winmm_test.exe.so winmm_test.exe.so && strip winmm_test.exe.so cp ../../dlls/winspool/tests/winspool.drv_test.exe.so winspool.drv_test.exe.so && strip winspool.drv_test.exe.so cp ../../dlls/winsock/tests/ws2_32_test.exe.so ws2_32_test.exe.so && strip ws2_32_test.exe.so LD_LIBRARY_PATH="../../libs/unicode:$LD_LIBRARY_PATH" ../../tools/wrc/wrc --nostdinc -I. -I. -I../../include -I../../include -fogui.res gui.rc *** Error code 1 Stop in /usr/home/vertigo/winecvs/programs/winetest. *** Error code 1 Stop in /usr/home/vertigo/winecvs/programs. *** Error code 1 Stop in /usr/home/vertigo/winecvs. -------------------------------------------------- at this point, i'm at a loss... i've made sure that the kernel had all the options that wine wants, because i did them when i set smp and apic_io... if anyone out there can help me out with this, it would be much appreciated. thanks in advance. shaun

1 0

EM_UNDO message handling for single line edit controls
by Santosh Siddheshwar 21 Apr '04

21 Apr '04

Hi, I think there is a defect in the handling of EM_UNDO message for single line edit controls. If you go by what MSDN says this message should always return TRUE. But in EDIT_EM_Undo method (controls/edit.c) we are checking whether the style of the edit control is Read Only and returning FALSE if it is Read Only. My question is why should a read only edit control not be allowed to handle WM_PASTE, EM_UNDO and similar messages? Regards Santosh Siddheshwar ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

Re: winetest: timeout & no consoles
by Dimitrie O. Paun 21 Apr '04

21 Apr '04

On April 19, 2004 6:27 pm, Ferenc Wagner wrote: > - force a 2-minute timeout on individual tests. Nice. I hope it's not too short. Does dissect & gather correctly recognize (and reflect on the HTML page) these timeouts? I'd be nice (and important :)) to know about them. -- Dimi.

2 2

Strnage fff-by-one error
by Dimitrie O. Paun 20 Apr '04

20 Apr '04

Folks, This is weird one. The Winelib build of AbiWord exposes an off-by-one error. However, the Win32 build of AbiWord works perfectly (without this very problem) under Wine/ReactOS/Windows. AbiWord builds flawlessly under Winelib, not even a warning, so my guess one of our constants is off by one. The bug must appear in their code while building it, since our code to execute the Winelib app and the Win32 app is byte for byte identical. I've attached a few screenshots to demonstrate what happens when you open a menu/dialog/etc and then you close it. Namely, the invalidation (or rather painting) is off by one at right & bottom of the invalidated rectangle. -- Dimi.

4 4

Re: RFH: winetest testing
by Mehmet YASAR 20 Apr '04

20 Apr '04

> 4. Programme stops on "user32:input" (the progressbar is at about 90%) Sorry, I made a mistake. I thought tests stopped on "user32:input" whereas there were running. After waiting I see a timeout error and a dialog box asking to send data to server.

1 0

Re: Replace winedefault.reg with wine.inf in README, README.it and PACKAGING
by Lionel Ulmer 20 Apr '04

20 Apr '04

On Tue, Apr 20, 2004 at 09:14:28PM +0200, Ivan Leo Murray-Smith wrote: > As in subject. > License: LGPL * An initial set of registry entries. The current Wine standard is to use the regedit tool against - the 'winedefault.reg' file to generate a default registry. + the 'wine.ing' file to generate a default registry. The current preferred method of configuring/installing It's not 'use the regedit tool against...' but the 'rundll32 tool'. Lionel -- Lionel Ulmer - http://www.bbrox.org/

1 0

DateTimeCtrl doesn't select a new date
by Felipe W Damasio (Elipse Software) 20 Apr '04

20 Apr '04

Greetings, Whe using CDateTimeCtrl and selecting a new date on that calendar thing, the date isn't selected and the widnow isn't closed. In fact, there's no way I can close that window, except closing the program. Attached is a little app Cesar Mello <cesar(a)elipse.com.br> wrote to show this problem. Also attached is the Windows' binary for testing purposes. Tested with the latest wine. Please let me know if I can provide any more info to help this fixed. Thanks in advance, Felipe

3 4

Re: wine/programs/winetest main.c Makefile.in
by Ferenc Wagner 20 Apr '04

20 Apr '04

Alexandre Julliard <julliard(a)winehq.org> writes: > ChangeSet ID: 12069 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2004/04/19 23:00:07 > > Log message: > Ferenc Wagner <wferi(a)afavant.elte.hu> > - Change to console mode so that winetest runs under WinRash. > - Move from spawnvp() to CreateProcess(). > - Force a 2-minute timeout on individual tests. > > Patch: http://cvs.winehq.org/patch.py?id=12069 Hi Alexandre, Is there a forcing reason to have oldstdout initialized to -1 besides playing safe? Not that I object it, just want to avoid grave errors in the future. -- Feri.

2 1

winetest: what next?
by Dimitrie O. Paun 20 Apr '04

20 Apr '04

OK, So assume we get the show rolling, tests will run on various boxes, results will be send back to WineHQ, nice colorful pages will be generated, and a beautiful index page will put all these together, being linked from the Status (http://www.winehq.org/site/status) page. Are we done? I think not. This is a very important piece of infrastructure, and it's buried rather deep into the bowels of WineHQ. Moreover, it's not easy to monitor the changes in testing status. As such, I would like to have a "Weekly testing update" posted to in the News section, with stuff like: how many tests were added, how many failed/successed, etc. since last week. Maybe a list of DLLs where changes were observed, and so on. To get these statistics (and possibly other interesing bits) in the future, I'm thinking at storing all these test results in the database. NB: I'm not proposing that we change the current processing of dissect & gather, it is very nice, and it's a big bonus that it works without a database. All I'm saying is that we can augment dissect to also save stuff to the database. For the database, we need two simple tables: wine_test_releases, and wine_test_results. wine_test_releases: build_id VARCHAR(20) NOT NULL cvs_ts VARCHAR(20) cvs_tag VARCHAR(20) url VARCHAR(256) NOT NULL publish_ts TIMESTAMP NOT NULL This table will be populated by Brian's script, when a new release is publised. One of cvs_ts or cvs_tag will be NOT NULL, and will specify how to get to the exact source used for the build. Nightly builds will use cvs_ts (cvs -D <cvs_ts>), while official releases done by Alexander will use cvs_tag (cvs -r <cvs_tag>). Additional metadata may be required here, suggestions welcome. wine_test_results: build_id VARCHAR(20) NOT NULL tester_id VARCHAR(20) test_name VARCHAR(20) NOT NULL subtest_name VARCHAR(40) NOT NULL file_name VARCHAR(128) NOT NULL line_number INTEGER NOT NULL result INTEGER // 0 = success, 1 = timeout, etc windows_version VARCHAR (15) // 4.3.1233 I've probably missed something, so feel free to add to this. Comments, flames? -- Dimi.

3 3

Winetest results uploaded... where?
by Jakob Eriksson 20 Apr '04

20 Apr '04

winetest.exe from http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ works fine for me in Windows XP, but where is the stuff uploaded? "test.winehq.org", ok fine, but where is the info going? regards, Jakob

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel