Howdy Wine users! The list of bugs with downloads that haven't been checked on in a while has gotten pretty long (1,359! as of May 6, 2009). If you're a moderate to advanced user of wine, please help by downloading and testing these applications and testing these bugs. Be sure you're using a recent version of wine (1.1.20 or git) and testing in a clean WINEPREFIX. Quick guide: 1) Pick random bug. 2) Download application to test. 2A) If download is busted/no longer available, leave a comment saying this. 3) Test for the bug. 4) If it's fixed, ask the original reporter to retest. 5) If it's still broken, leave a note so we know the bug is still there.
On Wed, May 6, 2009 at 6:07 AM, austin987 <wineforum-user at winehq.org> wrote:> Howdy Wine users! > > The list of bugs with downloads that haven't been checked on in a while has gotten pretty long (1,359! as of May 6, 2009). > > If you're a moderate to advanced user of wine, please help by downloading and testing these applications and testing these bugs. > > Be sure you're using a recent version of wine (1.1.20 or git) and testing in a clean WINEPREFIX. > > Quick guide: > 1) Pick random bug. > 2) Download application to test. > 2A) If download is busted/no longer available, leave a comment saying this. > 3) Test for the bug. > 4) If it's fixed, ask the original reporter to retest. > 5) If it's still broken, leave a note so we know the bug is still there.Looks like I forgot the link: http://bugs.winehq.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Wine&target_milestone=---&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=download&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=old+%2B+download&query_based_on=old+%2B+download&field0-0-0=days_elapsed&type0-0-0=greaterthan&value0-0-0=90 -- -Austin
> ...If you're a moderate to advanced user of wine...What's the definition of a moderate user? Just wondering if I could be of any use...
austin987 wrote:> > has bugs that are 6 months old, which brings the list down to a more > manageable 281 (and more likely fixed as well). >Yes, that's what I did. I was giving a simple example on how to shorten the list. I was wondering about other, real, low hanging criteria. In my experience not all bug report can be handled quickly.
isn't anyway to automate this procedure? 1)get the patch 2) test the patch 3) do tests and report 4) clear the prefix :repeat
austin987 wrote:> > I'm not sure what else there is to trim down on, quickly. >I feared that... The problem is that bug checking right now seems an uphill battle. I see two approaches to sort it out: - more man-power (but calling for volunteers doesn't seem sufficient, hence my suggestion of bringing the bugs to the forum readers) - simplify bug checking (low-hanging fruit was a cheat in this direction) How about a test system which stores the downloadable files and has a script for the installation, execution (a bit like PlayOnLinux) and possibly bug checking. At least some semi-automation should be possible?
austin987 wrote:> > Sure, that'd be great, but that also takes a lot of manpower :-). >I understand, but it is an investment that could pay off to test applications at each wine release. But I didn't had in mind a full installer like PlayOnLinux. Rather, I would go to a bug report, press a button and: - if it is an installer, download it (from bugzilla or so for reliability), create a new prefix, create a launcher; - if the bug happens at run-time, then a configured installation with wineprefix is downloaded to my system, and sets up a launcher. Yes requires a lot of bandwith from Wine (or from someone else), and someone has to put the installation there. [/quote] Coincidentally, that's sort of what my Summer of Code project is about, so give it a couple months and it'll be semi there. -Austin[/quote] I went to check back your post and I'm wondering what you mean actually by "test graphical applications": can you give a brief idea on how this is done, ie, how to test graphical output?
austin987 wrote:> > then analyzing the logs for "test failed", "todo_fixed", etc. It's a > lot of work, but should help greatly. >Thanks for details and best wishes with your project. I think improvements in testing can have a big positive impact on Wine. Looking forward to see it.> > Keep in mind this is related to, but different from what you're proposing. >Well, I just found out others had proposed it before, Dan Kegel and AndrewRiedi had a GSoC proposal along the lines discussed before, using PlayOnLinux and wpkg scripts. (never heard about the latest).
austin987 wrote:> > Feel free to send a patch: > http://source.winehq.org/git/website.git >Hmm, I can't find forum pages here, eg, viewforum.php. Also, the git web ui has a search option but doesn't seem to be able to search for file names??