On Sun, 18 Apr 2004, Jakob Eriksson wrote:
> Thank you, thank you, thank you! :-)
Happy to help :)
Paul Millar
Paul Millar wrote:
Each build is identified by its time/date stamp (e.g.
winetest-20040418-1000.zip). There's a fair number of different files
available:
winetest-.zip- zip compressed version of winetest.exe
winetest-.zip.cookie - the md5sum of winetest.exe (sort of)
winetest-.zip.sig
On Sat, 17 Apr 2004, Kevin Koltzau wrote:
> I can yes, just need to work out the details
Ah, but the devil's in the detail. I might just be me, but it seems to be
an inordinately fiddly process, but one I think I've finally got figured
out.
Its now part of the new version of WRT, which I'll just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 17 Apr 2004, Dimitrie O. Paun wrote:
> 2. Cron job builds winetest.exe and publishes it on WineHQ
> Paul Miller / [IN PROGRESS]
( s/Miller/Millar/ BTW, its the Scottish spelling ;)
> We are however blocking at (2) ATM, and I'm not sure
Kevin Koltzau wrote:
I am capable of building this if needed.
I've put up a copy of winetest.exe built from current
CVS on http://www.plop.org/winetest.exe if you are
interested in taking a look
Excellent!
Running winetest.exe is one of my favourite things to do. :-)
Anyway, I packed it with
I can yes, just need to work out the details
On Saturday 17 April 2004 05:09 pm, Dimitrie O. Paun wrote:
> OK, perfect. Can you do this on a daily basis (from cron,
> say at 4am EST), and do the publishing stuff?
>
On April 17, 2004 4:14 pm, Kevin Koltzau wrote:
> I am capable of building this if needed.
> I've put up a copy of winetest.exe built from current
> CVS on http://www.plop.org/winetest.exe if you are
> interested in taking a look
OK, perfect. Can you do this on a daily basis (from cron,
say at 4am
I am capable of building this if needed.
I've put up a copy of winetest.exe built from current
CVS on http://www.plop.org/winetest.exe if you are
interested in taking a look
On Saturday 17 April 2004 01:12 pm, Brian Vincent wrote:
> I noticed Kevin Koltzau has been playing with cross-compiling, an
As it was written in the Book of "Dimitrie O. Paun" <[EMAIL PROTECTED]>:
>
> Now, (8) is not essential for testing, without it we can just go directly
> to the generated page. Again (1) is just nice to have for end users, we
> can test without it. We are however blocking at (2) ATM, and I'm not su
Dimitrie O. Paun wrote:
So maybe with the testing framework in place, people can start by
submitting a test, waiting for results, and then submitting the
implementation. Very XP-ish :), but also rather cool. One would
be able to easily test a hypothesis in about 24h on a large number
of different
On April 17, 2004 10:47 am, Jakob Eriksson wrote:
> Is everything else, the Windows service and so on already done?
I think so. Here is the current workflow and status:
1. Tester downloads winrash.exe installer and runs it (one time only)
Chris Morgan / [IN PROGRESS]
2. Cron job builds wi
Alexandre Julliard <[EMAIL PROTECTED]> writes:
> Peter Riocreux <[EMAIL PROTECTED]> writes:
>
>> It gives every impression of working for me, but I have only tested it
>> with one application.
>>
>> Suggestions for better extended error codes appreciated.
>
> Error codes should not be based on sug
Peter Riocreux <[EMAIL PROTECTED]> writes:
> "Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>
>> So maybe with the testing framework in place, people can
>> start by submitting a test, waiting for results, and then
>> submitting the implementation. Very XP-ish :), but also
>> rather cool. One woul
Peter Riocreux wrote:
>
> "Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>
> > On April 15, 2004 7:54 pm, Alexandre Julliard wrote:
> >> Error codes should not be based on suggestions, what you should do is
> >> write a small test program under Windows to find out the real codes.
I wrote a test pr
Sorry, mistyped the wine-patches address before ...
--- Begin Message ---
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On April 15, 2004 7:54 pm, Alexandre Julliard wrote:
>> Error codes should not be based on suggestions, what you should do is
>> write a small test program under Windows to f
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On April 15, 2004 7:54 pm, Alexandre Julliard wrote:
>> Error codes should not be based on suggestions, what you should do is
>> write a small test program under Windows to find out the real codes.
>
> Hopefully, this sort of thing will be easier on
On April 15, 2004 7:54 pm, Alexandre Julliard wrote:
> Error codes should not be based on suggestions, what you should do is
> write a small test program under Windows to find out the real codes.
Hopefully, this sort of thing will be easier once we have the testing
framework in place. For example,
On April 15, 2004 11:18 am, Peter Riocreux wrote:
> * This doesn't yet matter, since these handlers are not yet called...!
> + *
> + * Peter Riocreux ([EMAIL PROTECTED]) 2004-04-15
> + * Added error checking and now uses SetLastError()
> */
One more thing: please don't add this sort of thing
Peter Riocreux <[EMAIL PROTECTED]> writes:
> It gives every impression of working for me, but I have only tested it
> with one application.
>
> Suggestions for better extended error codes appreciated.
Error codes should not be based on suggestions, what you should do is
write a small test program
19 matches
Mail list logo