Re: Make test drill, next steps, call for help with Winetest

2007-11-01 Thread Paul Vriens
Francois Gouget wrote: > On Sat, 27 Oct 2007, Francois Gouget wrote: > In fact I've been able to verify that it works in real life since > winetest has not been updated since last monday :-( > Compilation problems? Yeah, I guess due to the new d3dx8 tests. Have a look at http://quisquiliae.physi

Re: Make test drill, next steps, call for help with Winetest

2007-11-01 Thread Francois Gouget
On Sat, 27 Oct 2007, Francois Gouget wrote: [...] > There are other options to specify which version of winetest.exe to > grab, to set the timeout on the tests execution, etc. > > Things still on the todo list: > * the script also grabs the winetest.exe signature and attempts to > verify it. Bu

Re: Make test drill, next steps, call for help with Winetest

2007-10-29 Thread Jakob Eriksson
Francois Gouget wrote: > While I prefer the autorun approach because it has fewer dependencies on > the Windows side and thus allows me to test in as clean a Windows as > desired, your approach could be pretty useful for testing on a real > Windows machine. Maybe if you post your script with som

Re: Make test drill, next steps, call for help with Winetest

2007-10-29 Thread Francois Gouget
On Sat, 27 Oct 2007, Jakob Eriksson wrote: [...] > I achieved much the same thing by putting a wget script in the > Auto-startup folder of Windows. Then I copy in this vmware windows > virtual machine and start it. Then Windows itself downloads winetest > and upon completion, does a shutdown -h

Re: Make test drill, next steps, call for help with Winetest

2007-10-29 Thread Francois Gouget
On Sun, 28 Oct 2007, Detlef Riekenberg wrote: > On Sa, 2007-10-27 at 14:03 +0200, Francois Gouget wrote: > > > > Things still on the todo list: > > * the script also grabs the winetest.exe signature and attempts to > > verify it. But I don't know where to find the corresponding public > > key

Re: Make test drill, next steps, call for help with Winetest

2007-10-28 Thread Detlef Riekenberg
On Sa, 2007-10-27 at 14:03 +0200, Francois Gouget wrote: > > Things still on the todo list: > * the script also grabs the winetest.exe signature and attempts to > verify it. But I don't know where to find the corresponding public > key > (651FD487) so I don't know if this really works. Paul's

Re: Make test drill, next steps, call for help with Winetest

2007-10-27 Thread Jakob Eriksson
Hans Leidekker wrote: > On Saturday 27 October 2007 14:03:02 Francois Gouget wrote: > > >> That's something I've wanted to do for some time and this finally >> spured me to action. So here's a script that will do essentially the >> same thing but with VMware Workstation. >> > > Cool! I th

Re: Make test drill, next steps, call for help with Winetest

2007-10-27 Thread Hans Leidekker
On Saturday 27 October 2007 22:29:00 Jakob Eriksson wrote: > I often find cygwin a relief when working with Windows. Yes, I also run cygwin on my Windows guests. I have openssh running on them and export the Wine tree to the guests via samba so I can do: $ make crosstest $ ssh vm /cygdrive/w/d

Re: Make test drill, next steps, call for help with Winetest

2007-10-27 Thread Hans Leidekker
On Saturday 27 October 2007 14:03:02 Francois Gouget wrote: > That's something I've wanted to do for some time and this finally > spured me to action. So here's a script that will do essentially the > same thing but with VMware Workstation. Cool! I think I'll borrow some of your nice extra opti

Re: Make test drill, next steps, call for help with Winetest

2007-10-27 Thread Francois Gouget
On Mon, 15 Oct 2007, Hans Leidekker wrote: [...] > I have written attached script to facilitate automated winetest runs. > It needs a VirtualBox virtual machine with either Windows or a Wine platform > configured to run autorun.inf files. > worry about winetest screwing up your installation. [...]

Re: Make test drill, next steps, call for help with Winetest

2007-10-19 Thread Paul Vriens
Jeremy White wrote: >> Why can't you just run the winetest executable under Wine? Or do you mean >> you've >> changed some of the tests and want to see the results immediately? > > Because that's not logically correct. I am trying to run a regression > test on my current source tree. It *may*

Re: Make test drill, next steps, call for help with Winetest

2007-10-19 Thread Jeremy White
> Why can't you just run the winetest executable under Wine? Or do you mean > you've > changed some of the tests and want to see the results immediately? Because that's not logically correct. I am trying to run a regression test on my current source tree. It *may* be identical to the one most

Re: Make test drill, next steps, call for help with Winetest

2007-10-19 Thread Paul Vriens
Dimi Paun wrote: > > The plan was to have a home page at: > http://test.winehq.org > that would contain the explanation, plus an > index for the tests (hopefully organized nicely). > > That didn't happen... Yeah, I had some thoughts about that that were also discussed in the past but never

Re: Make test drill, next steps, call for help with Winetest

2007-10-19 Thread Paul Vriens
Jeremy White wrote: > In my opinion, it needs the following: > > 1. A Wiki page! > > I could not find *any* documentation on this utility. > > For example, I'm still not entirely clear on how to > setup and/or register my build.id so that my results > are available on

Re: Make test drill, next steps, call for help with Winetest

2007-10-15 Thread Detlef Riekenberg
On Mo, 2007-10-15 at 12:16 -0400, Dimi Paun wrote: > (And the rather > > non intuitive requirement to 'know' the unpublished > > url http://test.winehq.org/data/ is harsh). > > The plan was to have a home page at: > http://test.winehq.org > that would contain the explanation, p

re: Make test drill, next steps, call for help with Winetest

2007-10-15 Thread Dan Kegel
>> There is a headless operation mode already, it detects >> if you run it as a service, and skips appropriate tests. > > Perhaps on Windows; I'm focused on Linux. How about wine net start winetest? - Dan

Re: Make test drill, next steps, call for help with Winetest

2007-10-15 Thread Hans Leidekker
I have written attached script to facilitate automated winetest runs. It needs a VirtualBox virtual machine with either Windows or a Wine platform configured to run autorun.inf files. The script downloads the latest winetest binary and puts it in an iso image, along with an autorun file to trigge

Re: Make test drill, next steps, call for help with Winetest

2007-10-15 Thread Dimi Paun
On Mon, 2007-10-15 at 11:18 -0500, Jeremy White wrote: > Perhaps on Windows; I'm focused on Linux. Is there > a way to trigger that when doing a 'wine winetest.exe.so'? Maybe "-c" (console mode, no GUI) -- Dimi Paun <[EMAIL PROTECTED]> Lattica, Inc.

Re: Make test drill, next steps, call for help with Winetest

2007-10-15 Thread Jeremy White
> There is a headless operation mode already, it detects > if you run it as a service, and skips appropriate tests. Perhaps on Windows; I'm focused on Linux. Is there a way to trigger that when doing a 'wine winetest.exe.so'? Cheers, Jeremy

Re: Make test drill, next steps, call for help with Winetest

2007-10-15 Thread Dimi Paun
On Mon, 2007-10-15 at 10:48 -0500, Jeremy White wrote: > In my opinion, it needs the following: > > 1. A Wiki page! > > I could not find *any* documentation on this utility. > > For example, I'm still not entirely clear on how to > setup and/or register my build.id so that m