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
Mike Hearn mike@navi.cx 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.
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 :)
Mike Hearn mike@navi.cx 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... ;)
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
Jakob Eriksson jakov@vmlinux.org 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.
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.
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
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 :)
On Monday 17 January 2005 11:30, Ferenc Wagner wrote:
Jakob Eriksson jakov@vmlinux.org 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.
On Wed, Jan 12, 2005 at 05:29:36PM +0000, 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).
-
Dimitrie O. Paun -
Ferenc Wagner -
Jakob Eriksson -
Mike Hearn -
Paul Millar