Re: WineHQ:winetest: produce valid HTML
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://test.winehq.org/data/ is 2004-12-28. Also, the last tests build at SF is winetest-200409111000 which is a bit outdated :) What gives? -- Dimi.
Re: WineHQ:winetest: produce valid HTML
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? Going to http://test.winehq.com/ still yields an error, you have to know the magic URL and then navigate the builds manually. It'd be nice to get some pretty HTML frontend to that going: a task for somebody who is keen but doesn't want to hack Wine itself maybe? Could you elaborate your plan for winetest Feri? thanks -mike
Re: WineHQ:winetest: produce valid HTML
Am Mittwoch, 12. Januar 2005 18:14 schrieb Dimitrie O. Paun: > Cool stuff Feri. Anyone knows what happened to the tests? > The last one at http://test.winehq.org/data/ is 2004-12-28. > Also, the last tests build at SF is winetest-200409111000 > which is a bit outdated :) > Well, since 2004-12-28 we got test for msi.dll and two new GUIDs not supported by current(?) mingw. The attached patch fixes mingw for me. Hope i got the GUIDs right. As far i know the test are build at / uploaded to http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ by Paul Millar. Bye Stefan --- w32api/lib/uuid.c.sav 2005-01-06 23:21:03.0 +0100 +++ w32api/lib/uuid.c 2005-01-06 23:23:00.0 +0100 @@ -35,6 +35,7 @@ DEFINE_GUID(CLSID_AllClasses,0x330,0,0,0xc0,0,0,0,0,0,0,0x46); DEFINE_GUID(CLSID_CColorPropPage,0xbe35201,0x8f91,0x11ce,0x9d,0xe3,0,0xaa,0,0x4b,0xb8,0x51); DEFINE_GUID(CLSID_CFontPropPage, 0x0be35200,0x8f91,0x11ce,0x9d,0xe3,0x00,0xaa,0x00,0x4b,0xb8,0x51); +DEFINE_GUID(CLSID_CMultiLanguage, 0x275c23e2, 0x3747, 0x11d0, 0x9f,0xea,0x00,0xaa,0x00,0x3f,0x86,0x46); DEFINE_GUID(CLSID_CPicturePropPage,0xbe35202,0x8f91,0x11ce,0x9d,0xe3,0,0xaa,0,0x4b,0xb8,0x51); DEFINE_GUID(CLSID_ConvertVBX,0xfb8f0822,0x164,0x101b,0x84,0xed,0x8,0,0x2b,0x2e,0xc7,0x13); DEFINE_GUID(CLSID_CurrentUserClasses,0x332,0,0,0xc0,0,0,0,0,0,0,0x46); @@ -187,6 +188,7 @@ DEFINE_GUID(IID_ILockBytes,0xa,0,0,0xc0,0,0,0,0,0,0,0x46); DEFINE_GUID(IID_IMalloc,0x2,0,0,0xc0,0,0,0,0,0,0,0x46); DEFINE_GUID(IID_IMallocSpy,0x1d,0,0,0xc0,0,0,0,0,0,0,0x46); +DEFINE_GUID(IID_IMAPIPropData,0x2031A,0,0,0xC0,0,0,0,0,0,0,0x46); DEFINE_GUID(IID_IMarshal,0x3,0,0,0xc0,0,0,0,0,0,0,0x46); DEFINE_GUID(IID_IMessageFilter,0x16,0,0,0xc0,0,0,0,0,0,0,0x46); --- /dev/null 2003-09-23 19:59:22.0 +0200 +++ w32api/lib/msi.def 2005-01-06 23:18:33.0 +0100 @@ -0,0 +1,16 @@ +LIBRARY MSI.DLL +EXPORTS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: WineHQ:winetest: produce valid HTML
"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://test.winehq.org/data/ is 2004-12-28. > Also, the last tests build at SF is winetest-200409111000 > which is a bit outdated :) Yes, looks like Kevin had to give up on cross building the binaries a couple of months ago; it was he who updated the SF downloads page. Paul Millar, however, kept up with the load until the new GUIDs broke MinGW again. We already talked about the issue and Hans Leidekker also confirmed the MinGW problem, but hasn't got around to provide a patch yet. If Paul can use Stefan's patch, then new builds can be expected real soon, I guess. -- Feri.
Re: WineHQ:winetest: produce valid HTML
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, but keep it secret, of course. Still I can tell the only item of real interest is adding a Tag input field to the binary, which was brought forward by the apparent need of interactive and visible runs. > Going to http://test.winehq.com/ still yields an error, > you have to know the magic URL and then navigate the > builds manually. Ok, perhaps I can give out the classified URL: http://test.winehq.org/data/ Yes, you have to navigate manually (the links on the top don't work), but I've got Jeremy Newmann's word on knocking something up by yesterday. That something includes making those links work at least. > It'd be nice to get some pretty HTML frontend to that > going: a task for somebody who is keen but doesn't want to > hack Wine itself maybe? Yes, unless Jer has actually done it. Turning it into a template would also be possible, but I'm not too keen on it as that would steal real screen estate. But would be a nice touch, for sure. > Could you elaborate your plan for winetest Feri? 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. -- Yours, Feri.
Re: WineHQ:winetest: produce valid HTML
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 you easily navigate the available builds. Also clicking on the info/name links gives a 404 right now in many cases, so ... just making it feel more like a full website and some extra polish really :)
Re: WineHQ:winetest: produce valid HTML
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 you > easily navigate the available builds. In the works (Jer?) What kind of navigation would you prefer? Is forward/backward and a directory list (like flashy PHP frontend) enough? Do you want such buttons scattered on the page? A directory button, perhaps? Web design is surely not my strength... > Also clicking on the info/name links gives a 404 right now > in many cases, so ... Yes, that's the effect of putting new skin on an old body: old submissions simply don't have that information available separately. Tests submitted and processed after the commit (not more than two so far, I think) don't have this problem. I didn't want to complicate the code with conditionaly emitting the links; those tests are old and of limited interest only. Hope we'll get new binaries soon. > just making it feel more like a full website and some > extra polish really :) D'oh, aesthetics... ;) -- Feri.
Re: WineHQ:winetest: produce valid HTML
On Wednesday 12 January 2005 04:12 pm, Ferenc Wagner wrote: > Yes, looks like Kevin had to give up on cross building the > binaries a couple of months ago; it was he who updated the > SF downloads page. I actually gave up keeping the sourceforge upload working, I am however still building winetest. Sourceforge made some changes to their site that broke sfutils. I had thought about hosting the builds on wine.sourceforge.net, which I mentioned on the list some time ago with no response.
Re: WineHQ:winetest: produce valid HTML
On Wed, Jan 12, 2005 at 05:29:36PM +, Mike Hearn wrote: > Is there a todo list of what needs to be done for winetest anywhere? This is what I had in mind: * We need a page under http://www.winehq.org/site/status (in the right-hand box) which should contain: -- an explanation for the entire winetest business -- ditto for winrash (http://winrash.sf.net) -- pointers to where they can download them (tests & winrash) -- how they can help by actually running them (winrash is preferred) -- instructions on how to install winrash -- a legend for the test pages -- links to the last 10 most recent results * Also, http://test.winehq.org/ should contain: -- a short description of the results -- a link to the http://www.winehq.org/site/status, for full details -- the above mentioned legend for the results -- a summary with links to all test results (for bonus points, display them in calendar form). -- Dimi.
Re: WineHQ:winetest: produce valid HTML
On Wed, Jan 12, 2005 at 06:58:19PM -0500, Kevin Koltzau wrote: > I actually gave up keeping the sourceforge upload working, I am however > still building winetest. Sourceforge made some changes to their site that > broke sfutils. I had thought about hosting the builds on wine.sourceforge.net, > which I mentioned on the list some time ago with no response. Hmm, that would be cool. For reasons I can not understand, I can not access Paul's site at www.astro.gla.ac.uk, so having them available somewhere else would be very good for me. -- Dimi.
Re: WineHQ:winetest: produce valid HTML
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. > > As far i know the test are build at / uploaded to > http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ > by Paul Millar. Yes. I've taken your patch, Stefan, and integrated it with the collection of patches I'm currently using. Unfortunately, just including the file interferred with some of the patches that were already included (oops!). I'm rebuilding the mingw tool-chain as I type, so should have things ready first thing in the morning. I'll test it, and if it works, put it into production. Cheers, Paul. pgpBSGXUimwjF.pgp Description: PGP signature
Re: WineHQ:winetest: produce valid HTML
On Wednesday 12 January 2005 21:12, Ferenc Wagner wrote: > If Paul can use Stefan's patch, then new builds can be > expected real soon, I guess. Should be up tomorrow, all things being equal (and a following wind ;^) Paul. pgpcyHA6UAyeh.pgp Description: PGP signature
Re: WineHQ:winetest: produce valid HTML
On Thursday 13 January 2005 00:41, Dimitrie O. Paun wrote: > Hmm, that would be cool. For reasons I can not understand, I can > not access Paul's site at www.astro.gla.ac.uk, so having them > available somewhere else would be very good for me. Yes, this problem again? I've never heard of problems from anyone else. Currently, the DB backend that supplies the (stagnant) information for WRT is down, but the page degrades gracefully enough. The rest of the content is static, so should be visable to anyone. Could you do a bit more investigation, like "host www.astro.gla.ac.uk"? Ta, Paul. pgprjnwUFC0K1.pgp Description: PGP signature
Re: WineHQ:winetest: produce valid HTML
"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.
Re: WineHQ:winetest: produce valid HTML
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 tomorrow, all things being equal (and a following > wind ;^) Good work, guys! -- Thanks, Feri.
Re: WineHQ:winetest: produce valid HTML
On Thu, Jan 13, 2005 at 01:11:35AM +, Paul Millar wrote: > Could you do a bit more investigation, like "host > www.astro.gla.ac.uk"? Here you go: [EMAIL PROTECTED] ~]$ host www.astro.gla.ac.uk www.astro.gla.ac.uk is an alias for terra.astro.gla.ac.uk. terra.astro.gla.ac.uk has address 130.209.45.194 [EMAIL PROTECTED] ~]$ traceroute www.astro.gla.ac.uk traceroute to terra.astro.gla.ac.uk (130.209.45.194), 30 hops max, 38 byte packets 1 lattica.com (192.168.3.1) 0.519 ms 0.404 ms 0.331 ms 2 * * * 3 gw03-vlan201.wlfdle.phub.net.cable.rogers.com (66.185.90.161) 18.194 ms 6.477 ms 35.257 ms 4 gw01-vlan962.wlfdle.phub.net.cable.rogers.com (66.185.93.69) 8.538 ms 8.966 ms 25.388 ms 5 gw02.wlfdle.phub.net.cable.rogers.com (66.185.80.130) 14.756 ms 8.939 ms 52.187 ms 6 * * * 7 p13-0.core02.ord01.atlas.cogentco.com (66.28.4.213) 25.295 ms 22.545 ms 23.932 ms 8 p15-0.core01.ord03.atlas.cogentco.com (154.54.2.242) 22.971 ms 24.112 ms 24.849 ms 9 4.68.127.129 (4.68.127.129) 69.403 ms 36.608 ms 66.020 ms 10 so-2-1-0.bbr2.Chicago1.Level3.net (209.244.8.13) 57.766 ms 78.712 ms 37.232 ms 11 so-2-0-0.bbr2.Washington1.Level3.net (209.247.10.130) 35.877 ms 69.783 ms 39.840 ms 12 as-0-0.bbr1.London2.Level3.net (4.68.128.101) 111.231 ms 164.851 ms 180.228 ms 13 ge-3-0-0.gar1.London2.Level3.net (4.68.124.62) 102.045 ms 105.203 ms 103.338 ms 14 195.50.116.202 (195.50.116.202) 136.914 ms 144.620 ms 125.928 ms 15 po2-0.lond-scr4.ja.net (146.97.35.221) 114.603 ms 136.163 ms 101.644 ms 16 po1-0.read-scr.ja.net (146.97.33.26) 101.265 ms 112.260 ms 124.663 ms 17 po3-0.warr-scr.ja.net (146.97.33.54) 105.411 ms 106.434 ms 113.055 ms 18 po2-0.glas-scr.ja.net (146.97.33.58) 158.310 ms 119.836 ms 151.558 ms 19 po0-0.glasgow-bar.ja.net (146.97.35.54) 110.029 ms 110.312 ms 110.151 ms 20 146.97.40.106 (146.97.40.106) 152.059 ms 123.885 ms 111.152 ms 21 130.209.2.117 (130.209.2.117) 129.663 ms 160.970 ms 133.687 ms 22 130.209.2.2 (130.209.2.2) 112.559 ms 110.315 ms 123.665 ms 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * -- Dimi.
Re: WineHQ:winetest: produce valid HTML
On Thu, Jan 13, 2005 at 02:24:21AM +0100, Ferenc Wagner wrote: > Can't you even ping the server? If not, what does > traceroute say? If yes, your IP number must be blacklisted > at Glasgow... ;) No, I can't ping either: [EMAIL PROTECTED] ~]$ ping www.astro.gla.ac.uk PING terra.astro.gla.ac.uk (130.209.45.194) 56(84) bytes of data. --- terra.astro.gla.ac.uk ping statistics --- 24 packets transmitted, 0 received, 100% packet loss, time 22998ms -- Dimi.
Re: WineHQ:winetest: produce valid HTML
On Thu, 13 Jan 2005 01:11:35 +, Paul Millar <[EMAIL PROTECTED]> wrote: > On Thursday 13 January 2005 00:41, Dimitrie O. Paun wrote: > > Hmm, that would be cool. For reasons I can not understand, I can > > not access Paul's site at www.astro.gla.ac.uk, so having them > > available somewhere else would be very good for me. > > Yes, this problem again? I've never heard of problems from anyone > else. For what it's worth, I have no problem accessing http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ -Brian
Re: WineHQ:winetest: produce valid HTML
Dimi, Both these results are what I get from remote hosts that can access the web pages, so unfortunately don't shed any light on the issue. 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 cat /proc/sys/net/ipv4/tcp_default_win_scale Cheers, Paul. On Thursday 13 January 2005 01:57, Dimitrie O. Paun wrote: > On Thu, Jan 13, 2005 at 01:11:35AM +, Paul Millar wrote: > > Could you do a bit more investigation, like "host > > www.astro.gla.ac.uk"? > > Here you go: > > [EMAIL PROTECTED] ~]$ host www.astro.gla.ac.uk > www.astro.gla.ac.uk is an alias for terra.astro.gla.ac.uk. > terra.astro.gla.ac.uk has address 130.209.45.194 > > [EMAIL PROTECTED] ~]$ traceroute www.astro.gla.ac.uk > traceroute to terra.astro.gla.ac.uk (130.209.45.194), 30 hops max, > 38 byte packets 1 lattica.com (192.168.3.1) 0.519 ms 0.404 ms > 0.331 ms 2 * * * > 3 gw03-vlan201.wlfdle.phub.net.cable.rogers.com (66.185.90.161) > 18.194 ms 6.477 ms 35.257 ms 4 > gw01-vlan962.wlfdle.phub.net.cable.rogers.com (66.185.93.69) 8.538 > ms 8.966 ms 25.388 ms 5 gw02.wlfdle.phub.net.cable.rogers.com > (66.185.80.130) 14.756 ms 8.939 ms 52.187 ms 6 * * * > 7 p13-0.core02.ord01.atlas.cogentco.com (66.28.4.213) 25.295 ms > 22.545 ms 23.932 ms 8 p15-0.core01.ord03.atlas.cogentco.com > (154.54.2.242) 22.971 ms 24.112 ms 24.849 ms 9 4.68.127.129 > (4.68.127.129) 69.403 ms 36.608 ms 66.020 ms 10 > so-2-1-0.bbr2.Chicago1.Level3.net (209.244.8.13) 57.766 ms 78.712 > ms 37.232 ms 11 so-2-0-0.bbr2.Washington1.Level3.net > (209.247.10.130) 35.877 ms 69.783 ms 39.840 ms 12 > as-0-0.bbr1.London2.Level3.net (4.68.128.101) 111.231 ms 164.851 > ms 180.228 ms 13 ge-3-0-0.gar1.London2.Level3.net (4.68.124.62) > 102.045 ms 105.203 ms 103.338 ms 14 195.50.116.202 > (195.50.116.202) 136.914 ms 144.620 ms 125.928 ms 15 > po2-0.lond-scr4.ja.net (146.97.35.221) 114.603 ms 136.163 ms > 101.644 ms 16 po1-0.read-scr.ja.net (146.97.33.26) 101.265 ms > 112.260 ms 124.663 ms 17 po3-0.warr-scr.ja.net (146.97.33.54) > 105.411 ms 106.434 ms 113.055 ms 18 po2-0.glas-scr.ja.net > (146.97.33.58) 158.310 ms 119.836 ms 151.558 ms 19 > po0-0.glasgow-bar.ja.net (146.97.35.54) 110.029 ms 110.312 ms > 110.151 ms 20 146.97.40.106 (146.97.40.106) 152.059 ms 123.885 > ms 111.152 ms 21 130.209.2.117 (130.209.2.117) 129.663 ms > 160.970 ms 133.687 ms 22 130.209.2.2 (130.209.2.2) 112.559 ms > 110.315 ms 123.665 ms 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * pgp4SOPuPcj11.pgp Description: PGP signature
Re: WineHQ:winetest: produce valid HTML
On Wednesday 12 January 2005 22:12, Ferenc Wagner wrote: > SF downloads page. Paul Millar, however, kept up with the > load until the new GUIDs broke MinGW again. We already > talked about the issue and Hans Leidekker also confirmed the > MinGW problem, but hasn't got around to provide a patch yet. > If Paul can use Stefan's patch, then new builds can be > expected real soon, I guess. I've put a couple of new RPMs on my page: http://mirzam.it.vu.nl/mingw/ >From the changelog: - update mingw-runtime to 3.6 - update w32api to 3.2 - add mscms import library. - add msi import library. - add a uuid needed by MAPI tests - rebuild on Fedora Core 3 These allow me to cross build all tests in current cvs. -Hans
Re: WineHQ:winetest: produce valid HTML
On Thursday 13 January 2005 13:40, Hans Leidekker wrote: > On Wednesday 12 January 2005 22:12, Ferenc Wagner wrote: > > If Paul can use Stefan's patch, then new builds can be > > expected real soon, I guess. > > I've put a couple of new RPMs on my page: >http://mirzam.it.vu.nl/mingw/ OK, I've checked Hans' patches against Stefan's and found differences! I'm not a Windows person, so do these matter? In uuid.c, only the one difference: From Stefan +DEFINE_GUID(IID_IMAPIPropData,0x2031A,0,0,0xC0,0,0,0,0,0,0,0x46); From Hans +DEFINE_OLEGUID(IID_IMAPIPropData,0x2031A,0,0); In the msi.def, quite a few differences, picking one at random From Stefan [EMAIL PROTECTED] From Hans [EMAIL PROTECTED] @8 I don't really want to spend lots of time merging patches, so could one set be defined as "correct", and I'll use them. Cheers, Paul. Cheers, Paul. pgpvWJ0hZaXi7.pgp Description: PGP signature
Re: WineHQ:winetest: produce valid HTML
On Thursday 13 January 2005 15:23, Paul Millar wrote: > In uuid.c, only the one difference: > From Stefan > +DEFINE_GUID(IID_IMAPIPropData,0x2031A,0,0,0xC0,0,0,0,0,0,0,0x46); > From Hans > +DEFINE_OLEGUID(IID_IMAPIPropData,0x2031A,0,0); Both are correct (the DEFINE_OLEGUID resolves to the former). > In the msi.def, quite a few differences, picking one at random > From Stefan > [EMAIL PROTECTED] > From Hans > [EMAIL PROTECTED] @8 Again, both are OK. -Hans
Re: WineHQ:winetest: produce valid HTML
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 This is 0. One more thing to try is tcptraceroute: $ /usr/sbin/tcptraceroute www.astro.gla.ac.uk 80 Selected device eth0, address 157.181.170.74, port 41886 for outgoing packets Tracing the path to www.astro.gla.ac.uk (130.209.45.194) on TCP port 80, 30 hops max [...] 15 po3-0.warr-scr.ja.net (146.97.33.54) 45.120 ms 44.988 ms 45.036 ms 16 po2-0.glas-scr.ja.net (146.97.33.58) 49.367 ms 49.226 ms 49.186 ms 17 po0-0.glasgow-bar.ja.net (146.97.35.54) 49.115 ms 49.114 ms 49.057 ms 18 146.97.40.106 (146.97.40.106) 49.504 ms 50.188 ms 49.472 ms 19 130.209.2.117 (130.209.2.117) 49.783 ms 50.823 ms 49.629 ms 20 130.209.2.2 (130.209.2.2) 49.744 ms 49.599 ms 49.957 ms 21 terra.astro.gla.ac.uk (130.209.45.194) [open] 49.644 ms * * The interesting part may be filtered, but it was able to contact terra at port 80. -- Feri.
Re: WineHQ:winetest: produce valid HTML
Paul Millar wrote: On Thursday 13 January 2005 00:41, Dimitrie O. Paun wrote: Hmm, that would be cool. For reasons I can not understand, I can not access Paul's site at www.astro.gla.ac.uk, so having them available somewhere else would be very good for me. Yes, this problem again? I've never heard of problems from anyone else. It happens to me sometimes too. regards, Jakob
Re: WineHQ:winetest: produce valid HTML
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 can't believe I didn't think of this before, but the test results really should be sorted differently. I would prefer to have all failed tests at the top, so one could see easily which ones need to be fixed. It would also be nice if the author of a test got an email whenever a test failed. regards, Jakob
Re: WineHQ:winetest: produce valid HTML
Am Donnerstag, 13. Januar 2005 14:40 schrieb Hans Leidekker:
>
> I've put a couple of new RPMs on my page:
>
>http://mirzam.it.vu.nl/mingw/
>
> From the changelog:
>
> - update mingw-runtime to 3.6
> - update w32api to 3.2
> - add mscms import library.
> - add msi import library.
> - add a uuid needed by MAPI tests
> - rebuild on Fedora Core 3
>
> These allow me to cross build all tests in current cvs.
>
Hello Hans,
i had a build problem with the new rpms. The gcc rpm registers itself as
mingw-gcc-3.4.2-10hl, but the mingw rpm (runtime, w32api) requires
mingw-gcc-core for its build. Therefore i have changed gcc's spec file like
this:
diff -uw SPECS/mingw-gcc.spec.sav SPECS/mingw-gcc.spec
--- SPECS/mingw-gcc.spec.sav 2005-01-14 20:05:50.0 +0100
+++ SPECS/mingw-gcc.spec 2005-01-14 20:06:09.0 +0100
@@ -12,7 +12,7 @@
%define debug_package %{nil}
Summary: GCC, GNU Compiler Collection (C/C++ compiler) for MinGW/Wine.
-Name: mingw-%{appname}
+Name: mingw-%{appname}-core
Version: %{mainver}
Release: 10hl
Copyright: GPL
I will send you the SuSE 9.0 rpms on Monday from work. 11MB will take very
long over my analog line.
Bye Stefan
Re: WineHQ:winetest: produce valid HTML
On Friday 14 January 2005 21:31, Stefan Leichter wrote: > i had a build problem with the new rpms. The gcc rpm registers itself as > mingw-gcc-3.4.2-10hl, but the mingw rpm (runtime, w32api) requires > mingw-gcc-core for its build. Fixed now, thanks. -Hans
Re: WineHQ:winetest: produce valid HTML
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 ones need to be fixed. Not being an addition but a change, I'd like to hear others' opinion on this matter. My personal feeling is that losing alphabetical ordering on test names isn't worth it, as color monitors are fairly common nowadays. So vote for the change! > It would also be nice if the author of a test got an email > whenever a test failed. Finding out the author of a test isn't easy, it requires some digging into CVS. On the other hand, I'd choose an opt-in method instead. But it's a separate project anyway, the present machinery has pretty much nothing to facilitate this. The summary.txt files are easy to parse and available by HTTP, so one could use them to get the figures. -- Feri.
Re: WineHQ:winetest: produce valid HTML
On Mon, Jan 17, 2005 at 11:30:53AM +0100, Ferenc Wagner wrote: > > I would prefer to have all failed tests at the top, so one > > could see easily which ones need to be fixed. > > Not being an addition but a change, I'd like to hear others' > opinion on this matter. I agree, it's not worth losing alphabetical ordering. > > It would also be nice if the author of a test got an email > > whenever a test failed. > > Finding out the author of a test isn't easy, it requires > some digging into CVS. And we can't just do it, we need opt-ins, etc. Not worth it IMO. -- Dimi.
Re: WineHQ:winetest: produce valid HTML
Dimitrie O. Paun wrote: It would also be nice if the author of a test got an email whenever a test failed. Finding out the author of a test isn't easy, it requires some digging into CVS. And we can't just do it, we need opt-ins, etc. Not worth it IMO. But if I were to implement an opt-in scheme, you would be ok with it? regards, Jakob
Re: WineHQ:winetest: produce valid HTML
On Mon, Jan 17, 2005 at 03:05:09PM +0100, Jakob Eriksson wrote: > But if I were to implement an opt-in scheme, you would be ok with it? I wouldn't be opposed to it, but I'd advice against expanding so much effort for such little benefit. We have so much to do, it's not like we're looking for stuff to kill time :) -- Dimi.
Re: WineHQ:winetest: produce valid HTML
On Monday 17 January 2005 11:30, Ferenc Wagner wrote: > Jakob Eriksson <[EMAIL PROTECTED]> writes: > > I would prefer to have all failed tests at the top, so one > > could see easily which ones need to be fixed. > > Not being an addition but a change, I'd like to hear others' > opinion on this matter. My personal feeling is that losing > alphabetical ordering on test names isn't worth it, as color > monitors are fairly common nowadays. So vote for the change! I'd vote for tests staying in the same relative position from run to run (be that alphabetical or whatever). > > It would also be nice if the author of a test got an email > > whenever a test failed. > > Finding out the author of a test isn't easy, it requires > some digging into CVS. On the other hand, I'd choose an > opt-in method instead. But it's a separate project anyway, > the present machinery has pretty much nothing to facilitate > this. The summary.txt files are easy to parse and available > by HTTP, so one could use them to get the figures. One possibility is to send an email to the wine-devel list when something breaks (but only the one!). There were mixed reactions to this, for WRT, so I filtered all the emails and double-checked before forwarding them. Paul. pgpzevwbAydWR.pgp Description: PGP signature
