Vijay Kiran Kamuju infyqu...@gmail.com writes:
Can anyone tell me how to get that into the mainline kernel ASAP.
Or Anyone can send it on my behalf to lkml list to get it into main line
Why don't you send the patch to linux-...@vger.kernel.org?
--
Cheers,
Feri.
Jeremy Newman [EMAIL PROTECTED] writes:
http://wine.codeweavers.com/winehq_new/
Is it possible to add some preload magic for the impressed button
images? Otherwise the buttons disappear for a moment when I hover
above them the first time.
--
Cheers,
Feri.
Dmitry Timoshkov [EMAIL PROTECTED] writes:
Christopher [EMAIL PROTECTED] wrote:
Thanks for pointing that out! Am I suppose to attach a test case for all
my patches to wine-patches? I had submitted a testcase under the bug
report I filed, so I didn't attach it to the email.
You have to
Paul Vriens [EMAIL PROTECTED] writes:
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in
winetest? The rest of our programs do, but winetest uses malloc and
realloc.
I can't recall any. I'm more comfortable with the latter, since
winetest is the only Win32 application I've
Paul Vriens [EMAIL PROTECTED] writes:
Ferenc Wagner wrote:
Paul Vriens [EMAIL PROTECTED] writes:
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in
winetest? The rest of our programs do, but winetest uses malloc and
realloc.
I can't recall any. I'm more comfortable
Paul Vriens [EMAIL PROTECTED] writes:
'http://www.xs4all.nl/~pvriens/200708031000.new.single/' shows the new results
page for single tests. Instead of a single '.' there is a failure shown (red
box) and a skip border (as these tests have not run). There is still a '.'
which
could maybe
Paul Vriens [EMAIL PROTECTED] writes:
My idea is to visualize the skipped tests by using the blue border
at the single test level to indicate tests are skipped.
Hey, I like it! That blue border was already obsolete when I last
touched the code, but I found it so neat that I couldn't kill it
Paul Vriens [EMAIL PROTECTED] writes:
On Thu, 2006-11-30 at 13:11 -0500, Dimi Paun wrote:
On Thu, November 30, 2006 1:01 pm, Paul Vriens wrote:
I'm hitting the 1MB limit already with my win98 tests. Most other tests
are about to reach that threshold as well.
I'd make it 2MB, what's 1MB
Alexandre Julliard [EMAIL PROTECTED] writes:
Thomas Weidenmueller [EMAIL PROTECTED] writes:
LoadString() cannot be used to measure the length of a string resource.
It will not return the length of the string if no buffer is provided,
instead it will return 0! This patch fixes the broken
FYI:
From: Eike Lantzsch, ZP6CGE [EMAIL PROTECTED]
Date: Wed, 13 Jul 2005 11:59:36 -0400
Message-ID: [EMAIL PROTECTED]
I get errors when compiling current cvs.
.../wine# /wine/dlls/crypt32/tests/main.c:148:
undefined reference to `CertFindAttribute'
.../wine/dlls/crypt32/tests/encode.c:541:
Paul Millar [EMAIL PROTECTED] writes:
On Monday 25 April 2005 16:18, Alexandre Julliard wrote:
Paul Millar [EMAIL PROTECTED] writes:
Hopefully not a controversial one [...]
The problem with this is that the result is not a valid path, which
breaks tools that parse the output to let you
Hi,
I think this message better fits here on the devel list.
Cheers,
Feri.
Start of forwarded message
From: Jonathan Duncan [EMAIL PROTECTED]
Newsgroups: comp.emulators.ms-windows.wine
Date: 25 Mar 2005 10:26:46 -0800
Message-ID: [EMAIL PROTECTED]
I
Paul van Schayck [EMAIL PROTECTED] writes:
On Tue, 22 Mar 2005 09:52:13 -0500, Robert Reif [EMAIL PROTECTED] wrote:
What happens when you have two or more identical cards.
Should we also look for dmix in the device name?
I think we should always look for hw:n
I doubt it. First, ALSA have
Ivan Leo Puoti [EMAIL PROTECTED] writes:
Recently winetest is leaving a testdir directory behind
it, so cleanup needs to be done better.
This testdir comes from dlls/shell32/tests/shlfolder.c;
RemoveDirectoryA in line 78 can fail somehow. Also, the
return in line 147 doesn't do the necessary
Dmitry Timoshkov [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] wrote:
ChangeLog: Check desktop visibility after processing command
line arguments.
Why do you need it? There is no point to proceed if the
tests can not run in an appropriate environment.
The -s option
Dmitry Timoshkov [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] wrote:
The -s option (submit file, do not run tests) makes sense
anyway. But my main reason is that it drove me mad by not
obeying the -c option (no GUI) in some test runs. And I
don't think it hurts or contradicts
Steven Edwards [EMAIL PROTECTED] writes:
Like how to get winetest and the server to talk to each
other and what is needed in the build and url files.
programs/winetest/README contains some relevant information.
Is there some good documentation on how winrash and
winetest work and
Dmitry Timoshkov [EMAIL PROTECTED] writes:
let's see if IsWindowVisible() better detects a not visible desktop.
Ah, fine, this may put some momentum into the situation!
--
Feri.
Dmitry Timoshkov [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] wrote:
I was under the impression that most of the tests are
independent of desktop visibility.
Not really. Any API which directly or indirectly creates
windows or uses GDI is affected by the desktop visibility
Dmitry Timoshkov [EMAIL PROTECTED] writes:
I'd actually rise the question of sending the results of running winetest
on an invisible desktop under Windows. For instance I'm interested to see
how my recently added user32 tests behave on different Windows platforms,
but the tests which
Paul Vriens [EMAIL PROTECTED] writes:
in shlwapi/tests/shreg.c I've put two todo_wine statements
for obvious reasons (they fail, so do not test).
If I however look at
http://test.winehq.org/data/200502101000/wine_98/shlwapi:shreg.txt
These tests are executed! Any ideas what could be wrong?
If I run winetest-200502091000-paul-mingw manually on my win98 box
I get several messages Can't parse subtests output of for the
following tests [...]
just before the tests actually start.
In the first round winetest runs all the individual test
executables to find out the names of subtests
Paul Vriens [EMAIL PROTECTED] writes:
I have a Win98/WNT/W2K (on VMWare) and a XP Home
system. All are running the winrash service. All were
started when I was logged in but only the W98 and WNT were
considered running on a visible desktop.
Hmm, services use an invisible desktop by default
Paul Millar [EMAIL PROTECTED] writes:
I've been a bit busy lately so haven't gotten around to
fixing it, but should have some spare time tonight,
fingers crossed ;)
Hey, you did it! Thanks very much!
As a side note, the shell32:shlfolder test leaves an empty
testdir directory around when
Dmitry Timoshkov [EMAIL PROTECTED] writes:
Jakob Eriksson [EMAIL PROTECTED] wrote:
http://test.winehq.org/data/200501151000/2000_JakobEriksson/gdi32:metafile.txt
This fails. It shouldn't, because I ran winetest manually.
Ivan Leo Puoti [EMAIL PROTECTED] writes:
I've run tests twice, once with winrash and once manually, on windows nt 4.0
http://test.winehq.com/data/200501131000/#NT%204
interestingly some tests that fail or timeout when run from winrash,
work when
run manually.
Is there a way this could be
Jakob Eriksson [EMAIL PROTECTED] writes:
Ferenc Wagner wrote:
What makes you think I've got one? It should be *you*
who speak up and tell what information/presentation is
need for the best and easiest use.
I would prefer to have all failed tests at the top, so one
could see easily which
Paul Vriens [EMAIL PROTECTED] writes:
If the first CreateKey fails, there is no need to continue with the
testing (because the rest of the tests will fail as well). What's the
best way to stop there?, something like this?:
START_TEST(shreg)
{
HKEY hkey = create_test_entries();
+
Ivan Leo Puoti [EMAIL PROTECTED] writes:
Do you mean that the tagless report was generated by a
manual run while the one with the IvanLeo tag was run by
winrash?
Yes, those reports were both generated from the same
winetest binary. I'm not sure of what you mean by
crosschecks, but I'll do
Paul Millar [EMAIL PROTECTED] writes:
As a shot in the dark, have you got either ECN set, or a non-zero
default window-scaling? Which kernel are you running?
cat /proc/sys/net/ipv4/tcp_ecn
This gives 1 for me (and I can access your pages).
cat /proc/sys/net/ipv4/tcp_default_win_scale
Dimitrie O. Paun [EMAIL PROTECTED] writes:
On Wed, Jan 12, 2005 at 05:29:18PM +0100, Ferenc Wagner wrote:
ChangeLog: * Generate valid HTML 4.01 Strict.
* Underline vis_note class links, too.
Cool stuff Feri. Anyone knows what happened to the tests?
The last one at http
Mike Hearn [EMAIL PROTECTED] writes:
On Wed, 12 Jan 2005 17:29:18 +0100, Ferenc Wagner wrote:
ChangeLog: * Generate valid HTML 4.01 Strict.
* Underline vis_note class links, too.
Groovy! Is there a todo list of what needs to be done for
winetest anywhere?
I've got one myself
Mike Hearn [EMAIL PROTECTED] writes:
On Wed, 12 Jan 2005 22:26:18 +0100, Ferenc Wagner wrote:
What makes you think I've got one? It should be *you*
who speak up and tell what information/presentation is
need for the best and easiest use.
I basically did: some UI for test.winehq.com to let
Dimitrie O. Paun [EMAIL PROTECTED] writes:
For reasons I can not understand, I can not access Paul's
site at www.astro.gla.ac.uk
Can't you even ping the server? If not, what does
traceroute say? If yes, your IP number must be blacklisted
at Glasgow... ;)
--
Feri.
Paul Millar [EMAIL PROTECTED] writes:
On Wednesday 12 January 2005 20:09, Stefan Leichter wrote:
Am Mittwoch, 12. Januar 2005 18:14 schrieb Dimitrie O. Paun:
Anyone knows what happened to the tests?
[...] The attached patch fixes mingw for me. Hope i got the GUIDs
right.
Should be up
Mike McCormack [EMAIL PROTECTED] writes:
How hard to you think it would be to rig up a web page for
people to do translations for wine on?
Have a web page (translate.winehq.org?) into which we feed
in all the .rc files and maybe even parts of WineHQ, and
show the translations for each
Vincent Béron [EMAIL PROTECTED] writes:
Le mer 29/12/2004 à 05:38, Joris Huizer a écrit :
In debian the package is called libasound2-dev, version
0.9.0beta10.9.0beta1 which should be the 0.9 branch of alsa
Either update to alsa 1.0, downgrade Wine to prior
20040505, or switch to the
Mike Hearn [EMAIL PROTECTED] writes:
On Thu, 23 Dec 2004 17:01:09 +0200, Lauri Tulmin wrote:
Add tests for LBS_EXTENDEDSE and LBS_EXTENDEDSEL | LBS_MULTIPLESEL
listboxes. Some of these test don't pass on wine.
Thanks for the tests! If they don't pass in Wine though you need to
surround
Jakob Eriksson [EMAIL PROTECTED] writes:
Now without the linewrap.
I hate to say this, but it's still wrapped... :(
--
Feri.
Tero Tamminen [EMAIL PROTECTED] writes:
Yes. But will sticking to a fixed directory name (and
possibly file name) help, or does ZoneAlarm check eg. MD5
sums to thwart any countermeasure from our side? Anyway,
I have the feeling that this should be solved by
configuring ZoneAlarm instead of
Francois Gouget [EMAIL PROTECTED] writes:
On Thu, 9 Dec 2004, Tero Tamminen wrote:
[...]
So would it be possible to start all the tests from same
directory (I mean, every version of the tests would start
in same directory). It would save me some time because I
wouldn't have to click through
Jakob Eriksson [EMAIL PROTECTED] writes:
Do you agree, should we stop using winrash?
Dmitry Timoshkov [EMAIL PROTECTED] wrote:
Jakob Eriksson [EMAIL PROTECTED] wrote:
Well, I tried now marking the service as interactive,
but that didn't make any difference.
So, what follows, deprecate
Paul Millar [EMAIL PROTECTED] writes:
All things being equal tomorrow's build (presuming they'll
be one) will include binaries that refer to themselves
correctly.
Looks like you got it right. Thank you very much!
--
Feri.
Robert Reif [EMAIL PROTECTED] writes:
Winetest has a runningunderwine report option. Running
it under Wine will be supported.
winetest results from wine are not accepted by the website.
Yes they are. Just make dist.
To be really useful as a developer tool, you would need wine
specific
Jakob Eriksson [EMAIL PROTECTED] writes:
Dmitry Timoshkov wrote:
Ferenc Wagner [EMAIL PROTECTED] wrote:
Winrash, which invokes winetest in most of the cases, is a
service process running on an invisible desktop. Winetest
itself can happily run on the real visible desktop, it's
just
Dmitry Timoshkov [EMAIL PROTECTED] writes:
The question is what makes the tests create invisible
windows? Does winetest run as a service on a not visible
desktop? Anything else?
Winrash, which invokes winetest in most of the cases, is a
service process running on an invisible desktop.
Robert Reif [EMAIL PROTECTED] writes:
I would like to see winetest used for more than windows
compatibility and wine regressions. I would like to see it
used as a diagnostic tool for specific hardware and os
combinations and specific system configurations. [...]
Since most people probably
Robert Reif [EMAIL PROTECTED] writes:
Ferenc Wagner wrote:
Robert Reif [EMAIL PROTECTED] writes:
Couldn't winetest fill in the proper test results fields
necessary for acceptance when compiled to an exe.so and
run in wine?
Did you make dist in programs/winetest?
winetest-dist.exe
Robert Reif [EMAIL PROTECTED] writes:
For the built in wine, run with wine case, couldn't there be
reasonable default values rather than reading them from a file?
That's exactly what we wanted to avoid. Submitted results
should * not come from Wine but genuine Windows systems, and
*
Eric Pouech [EMAIL PROTECTED] writes:
ChangeLog:
- ctrl-c enabling flag is now inherited
- fixed console-related fields in RTL_USER_PROCESS_PARAMETERS
- various clean-up in kernel32.SetConsoleCtrlHandler
- only send a console event once to a process and not to
Saulius Krasuckas [EMAIL PROTECTED] writes:
It shows some message-box telling: Can't enumerate test
files: 1813
I couldn't reproduce it. Can you provide details (elf/pe
run, ...)?
--
Feri.
Saulius Krasuckas [EMAIL PROTECTED] writes:
On 27 Aug 2004, Vincent Béron wrote:
Just redirecting it to glibc would be trivial, but the problem is that's
not the Right Thing To Do (tm) as both don't have exactly the same
behavior, and that some apps rely on the msvcrt behavior (ie, break
Saulius Krasuckas [EMAIL PROTECTED] writes:
I think that's due to some additional \r\n-s in the output
of msvcrt_test.exe.so.
Actually, not quite. The problem is that msvcrt's output
functions aren't redirected by libc's filehandle operations,
so winetest doesn't get the output (it gets
Saulius Krasuckas [EMAIL PROTECTED] writes:
On Wed, 18 Aug 2004, Ferenc Wagner wrote:
Saulius Krasuckas [EMAIL PROTECTED] writes:
I think that's due to some additional \r\n-s in the output
of msvcrt_test.exe.so.
Actually, not quite. The problem is that msvcrt's output
functions aren't
Dmitry Timoshkov [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] wrote:
ChangeLog: The desktop process is not automatically
restarted under Win95, so stop killing it.
This patch causes test_shell_window tests fail under win2k SP4.
Please either fix the failures
Zach Gorman [EMAIL PROTECTED] writes:
My impression is that (1) could be handled by remembering
the default button (which, as Krishna Murthy has shown, is
not the same as the default button id) in the DIALOGINFO
structure.
Number (2), however, is more difficult. When a button
receives the
Mike Hearn [EMAIL PROTECTED] writes:
On Sun, 15 Aug 2004 11:23:07 +0200, Ferenc Wagner wrote:
Once you remembered the current (possibly inactive) default
button in DIALOGINFO, this should come for free. I hope at
most one button can be default in a dialog...
http://weblogs.asp.net
[EMAIL PROTECTED] writes:
http://osdn.dl.sourceforge.net/sourceforge/wine/winetest-200407091000-kevin-mingw.zip
I just tried that url and it worked. Many of the ones
I've tried in the past haven't and the cause seems to be
that the mirror chosen doesn't have the file.
Hmm, Sourceforge's
Paul Millar [EMAIL PROTECTED] writes:
The build failed. It looks like there's a bug in CVS. Both
CLSID_DirectSoundPrivate and DSPROPSETID_DirectSoundDevice defined multiple
times (the wine-version of mingw libraries and in the source).
Yes, there was a short discussion about this on
[EMAIL PROTECTED] writes:
What is the service doing with winrash options btw? The
installer stops, installs and starts the winrash service.
The installer uses /S for silent installs, otherwise it
will try to popup windows. Are you sure the service isn't
calling the installer with /S?
You
Hi (and sorry for the broken post),
the mapi32 tests call scInitMapiUtil, which pops up an alert
box saying something like (translating it) Your default
mailer application isn't capable of this operation, please
ensure that Outlook is configured as the default mailer.
This brings the tests to a
Jon Griffiths [EMAIL PROTECTED] writes:
the mapi32 tests call scInitMapiUtil, which pops up an alert
box saying something like (translating it) Your default
mailer application isn't capable of this operation, please
ensure that Outlook is configured as the default mailer.
This probably
Jon Griffiths [EMAIL PROTECTED] writes:
Windows XP Professional, in a network with roaming profiles
served by Samba. I don't know what is relevant.
Strange, I'd have assumed you'd have an extended mapi client
installed by deault. What is your default mail client?
If it's Control
Paul Millar [EMAIL PROTECTED] writes:
On Monday 19 July 2004 12:50, Ferenc Wagner wrote:
Can you (cross)build the directsound tests?
FWIW, yes:
http://www.astro.gla.ac.uk/users/paulm/wine/dsound_test-20040721.10-00.exe
Fine, that works, even. :) What an interesting experience
Hi,
I'm largely incompetent in this field, so please forgive my
fallacies in the comment below, but I felt sad reading
Steven Edwards [EMAIL PROTECTED] write:
--- Paul Davis [EMAIL PROTECTED] wrote:
PDB might not be able to fuss, but I will. I recently
asked about a way to figure out which
Hi,
please somebody enlighten me! How does this test work once
psapi_test.exe is linked with -lpsapi? How can a program
start at all without one of its hard dependencies?
START_TEST(module)
{
dll = LoadLibrary(psapi.dll);
if (!dll) {
trace(LoadLibraryA(psapi.dll) failed:
Uwe Bonnes [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] writes:
Hi, please somebody enlighten me! How does this test
work once psapi_test.exe is linked with -lpsapi? How can
a program start at all without one of its hard
dependencies?
START_TEST(module)
{
dll
Hi,
let me simply forward this message here. I can't take care
for these during the weekend, but would be happy to receive
comments on the harder parts when I'm back.
Bye,
Feri.
From: Andrew Ziem [EMAIL PROTECTED]
Newsgroups: comp.emulators.ms-windows.wine
Subject: winetest observations
Stefan Leichter [EMAIL PROTECTED] writes:
i noticed that not all dlls with unittests are listed
inside the Main summary of test.winehq.org. Missing dlls
are: iphlpapi, mapi32, msvcrtd, psapi, version
Is there any reason for this?
Not that I know of. Submitting a patch, thanks for pointing
Dimitrie O. Paun [EMAIL PROTECTED] writes:
Speaking of the test results, I've noticed the following problems:
1. Some errors reported in the summary
don't get reported in the differences.
Good catch, fixed (*)
2. The differences tables are inconsistent.
How can you say that?! Do
Dimitrie O. Paun [EMAIL PROTECTED] writes:
3. We are running multiple test _per_ build, but only
one is curretly reported. Currently, it says:
Main summary for build 200406171000
where '200406171000' is a link to the test. But since
we have multiple downloads, it should
Dimitrie O. Paun [EMAIL PROTECTED] writes:
On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
What's missing, what should be easier?
Now that you're asking: in the reports, I don't quite like
that a single report for Win95 is listed as OSR2 in the
main summary [...]
I tend
Dimitrie O. Paun [EMAIL PROTECTED] writes:
the email would be good, but not as the ID, the reports
will be much uglified (the names are already a bit long
right now).
We could easily chop those long tags to 6-7 chars. Shall we?
we should have a -M switch that just appends metadata to
the
Chris Morgan [EMAIL PROTECTED] writes:
the winetest results are sent back to winehq and can be
accessed via http://test.winehq.org/data/ Pretty
formatting of the results is coming soon ;-)
Do you mean somebody's already working on it or that I
should do it eventually? I'm back from the
Alexandre Julliard [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] writes:
Back to the topic: my main point is that the situation is
best expressed by a Makefile and solved by make. Best as
opposed to verbosity and complexity. I suppose this is also
a fairly workable scheme
Robert Reif [EMAIL PROTECTED] writes:
This patch adds msacm32 to the tests.
I'm not sure this is correct because I got a subtest parse
error on the test following the one I added (msvcrt). I
also only tested it with wine. Could someone knowledgeable
in this program please check and correct
Dimitrie O. Paun [EMAIL PROTECTED] writes:
On Tue, 4 May 2004, Ferenc Wagner wrote:
The msvcrt subtest parse error is a known redirection
issue: the msvcrt test is linked against msvcrt (wow) and
thus ignores the redirected libc filehandles. Tough.
Can e special case this guy somehow
Alexandre Julliard [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] writes:
It's almost a resend of my previous patch which seems MIA.
The only difference is that I removed the possible sequence
point screwups in the hope they were the reason for the drop.
New files: programs
Alexandre Julliard [EMAIL PROTECTED] writes:
Ferenc Wagner [EMAIL PROTECTED] writes:
My first implementation did exactly that. However, these
pieces of information have their places in the depencency
tree and I managed to screw up my build more often than not
without the help of make
Dimitrie O. Paun [EMAIL PROTECTED] writes:
Looking at them I see that in winetest/winetest.conf,
$root = /home/laxdragon/wine/tools/winetest;
$builds = $root/winetest.builds;
but on the other hand in service.cgi we have
Jakob Eriksson [EMAIL PROTECTED] writes:
+lockfileex_capable = dll_capable(kernel32, LockFileEx);
+if (lockfileex_capable)
+{
+/* Test for broken LockFileEx a la Windows 95 OSR2. */
+if (LockFileEx( handle, 0, 0, 100, 0, overlapped ))
Can I ask somebody to
Scott W Gifford [EMAIL PROTECTED] writes:
I ported to Winelib because I had a hard time capturing
stdout from the Windows console program properly just
running the .exe under Wine.
shoot in the darkTry wineconsole instead of wine, that may
work better./shoot in the dark
--
Feri.
Eric Pouech [EMAIL PROTECTED] writes:
The output redirection didn't work from a GUI app: the libc
streams weren't initialized and thus the output disappeared.
Wouldn't DETACHED_PROCESS result the same? It's not crucial
for winetest itself, but making it a console app helped
debugging
Paul Millar [EMAIL PROTECTED] writes:
On Fri, 23 Apr 2004, Kevin Koltzau wrote:
If I'm not fundamentally mistaken, I'll start along this
route. It can't be that hard. Kevin, Paul, please speak
up! Is the URL determined at build time or by the service
script? If so, it will have to
Hi,
this is with current CVS:
../../tools/winegcc/winegcc -B../../tools/winebuild -shared
../../../src/dlls/d3d8/d3d8.specbasetexture.o cubetexture.o d3d8_main.o device.o
directx.o drawprim.o indexbuffer.o resource.o shader.o stateblock.o surface.o
swapchain.o texture.o utils.o
Jakob Eriksson [EMAIL PROTECTED] writes:
Check out http://test.winehq.org/data/20040425-1000/ OSR2 shell32:string.
It says 0, but if you click, there seems to be some kind
of error. Is it the test output somehow erratic, or is
the log parser doing something bad?
Eric Pouech [EMAIL PROTECTED] writes:
Ferenc Wagner a écrit :
Eric Pouech [EMAIL PROTECTED] writes:
The second part, yes. But winetest must have been made
into a console app, so it pops up a console when it
starts.
why do you need a console?
Er, I don't know. Winetest itself doesn't
Jakob Eriksson [EMAIL PROTECTED] writes:
By killing processes left and right, I managed to get a 50 - megabyte log.
Maybe in the future we should link in bzip2 in winetest.exe to
compress logs before submitting?
No, we'd better fix the pipe tests. On Win9x/Me one can't
create named pipes
Andreas Mohr [EMAIL PROTECTED] writes:
Make people know how to reduce log size, using pipes.
Hi Andi!
Two notes:
1. The --debugmsg option is deprecated, people should use
the WINEDEBUG environmental variable instead.
2. Won't the pipe block until you read from it, then give
you all the
Dimitrie O. Paun [EMAIL PROTECTED] writes:
1. Multiple builds
For a given BUILD_ID, we can have reports comming from
different builds now, that is from different winetest-*.exe.
That means a much of URLs, etc.
That's abuse. :) BUILD_ID is intended to identify winetest,
not Wine. We can
Dimitrie O. Paun [EMAIL PROTECTED] writes:
On Fri, 23 Apr 2004, Ferenc Wagner wrote:
Dimitrie O. Paun [EMAIL PROTECTED] writes:
For a given BUILD_ID, we can have reports comming from
different builds now, that is from different winetest-*.exe.
That means a much of URLs, etc.
That's
Dimitrie O. Paun [EMAIL PROTECTED] writes:
BTW Feri, can we indent the body of our current sections?
The OS version section is already indented, although that's
optional an it's defined instead as a series of equations.
The only other section, Test output is not indented, and
that would go
Dimitrie O. Paun [EMAIL PROTECTED] writes:
Winetest will have to support a new option
-B filename
This will add a new section to the report,
just before the test results, called Build Info.
Why not to put this into a resource instead? I implemented
the URL option
Jakob Eriksson [EMAIL PROTECTED] writes:
On a side note, how about this:
int running_on_wine ()
{
HKEY version_key;
long size = 0;
RegCreateKeyEx (HKEY_LOCAL_MACHINE,
Yes, checking the registry is one way to detect Wine. But
not bulletproof, I'm afraid: what if somebody uses
Henk Poley [EMAIL PROTECTED] writes:
Ferenc Wagner wrote:
Henk Poley [EMAIL PROTECTED] writes:
Dimitrie O. Paun wrote:
Can you please run this .exe on your Windows box:
http://afavant.elte.hu/~wferi/wine/winetest.exe
We are trying to test the winetest infrastructure.
On my
Eric Pouech [EMAIL PROTECTED] writes:
The second part, yes. But winetest must have been made
into a console app, so it pops up a console when it
starts.
why do you need a console?
Er, I don't know. Winetest itself doesn't really need it,
but WinRash (the service) couldn't execute it
Dimitrie O. Paun [EMAIL PROTECTED] writes:
Paul, Kevin, Feri: it looks like we need to specify this
-mno-align-double when building the tests. Should this go
into Wine's Makefiles?
Sounds good, but I'm surely not the one to take the word of.
--
Feri.
Dimitrie O. Paun [EMAIL PROTECTED] writes:
On Wed, 21 Apr 2004, Dmitry Timoshkov wrote:
There are some problem with running tests under winetest.
For instance user/msg test fails when running under it,
but has no failures if ran as a standalone app.
We know, it's weird. Help fixing them is
Jakob Eriksson [EMAIL PROTECTED] writes:
when you click on one of the numbers to see the test
output, the summary line appears at the bottom of test
output. Like this one:
vartest: 553559462 tests executed, 0 marked as todo, 4113 failures.
It would be kinda neat to have that line at the
Jakob Eriksson [EMAIL PROTECTED] 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
1 - 100 of 184 matches
Mail list logo
