similar to: Performing a Regression Test

Hi, I try to do a regression test for the first time. I got in some kind of a loop, it looks like the bad commit isn't removed I'm stuck Here's how I went I found 1 bad commit 7cb044d3d8aaf1cee629c259f19177732bed37af is the first bad commit commit 7cb044d3d8aaf1cee629c259f19177732bed37af Author: Michael Stefaniuc <mstefani at redhat.de> Date: Wed Jul 21 23:56:02 2010 +0200

Hi, I do a regression testing actually for "AC : Brotherhood" because this game crash with wine 1.3.19 and not for old version. I read the wiki for the regression testing and i have questions for the test. To begin the test, i launch these command : Code: git bisect start git bisect good wine-1.3.18 git bisect bad wine-1.3.19 For exemple, i have Code: Bisecting: 150 revisions

Just to prove it, I replied to my own message...AND sent it to myself. What a day... -------- Original Message -------- Subject: Re: [Wine] Errors running BiblePro and BibleStudyPro on today's Git Date: Thu, 11 Feb 2010 20:07:43 -0700 From: James McKenzie <jjmckenzie51 at earthlink.net> To: James Mckenzie <jjmckenzie51 at earthlink.net> References:

Schuttwegraeumer <wineforum-user at winehq.org> wrote: >Sent: Aug 3, 2010 11:21 AM >To: wine-users at winehq.org >Subject: [Wine] Re: How to fix the SSL/https problem? > >Is that usefull?: If you want us to tell you that you are doing this right, yes. For location of errors, no. > > >> schutti at hell:~/Desktop/X/WINE/wine-git$ git bisect start >> schutti

Doh123, how is running a program off an NTFS partition asking for trouble? Ntfsprogs seems to handle it just fine. I know that NTFS doesn't let you mark a file as executable, and that the filesystem is susceptible to fragmentation, but you should just be able to tell it to run rather than display and be good. It shouldn't cause destruction. I think there might even be an NTFS defrag tool

jpka <wineforum-user at winehq.org> wrote: > > >> git reset --hard > >Thanks, it's works and very useful! >Now, how i, after some 'git bisect's, can i see where is set git tree currently precisely? git status might be the command you are looking for. The status line gives you the current commit from what I remember. >I study many git manuals but found

OK, so what is the answer to jsmith's question? On 6/22/08 wine-users-request at winehq.org wrote: > Message: 4 > Date: Sun, 22 Jun 2008 18:22:59 -0700 > From: James McKenzie <jjmckenzie51 at sprintpcs.com> > Subject: Re: [Wine] Wine on Windows XP > To: Michael Reich <reich.mikey at gmail.com> > Cc: wine-users at winehq.org > Message-ID: <485EFAF3.8010907

2014-02-11 11:41 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: > (b) bisect. you can (almost) definitely restrict the bisect to > drivers/gpu/drm/nouveau. if you have additional computational power, i > would recommend looking into distcc for speeding up the compiles. it > may be interesting to also try 3.6.x since 3.7 received a pretty big > rewrite. but a git bisect is a

Cesar Izurieta wrote: > I just deleted my .wine directory and run wineboot. The .wine > directory is recreated but I get: > > wine: created the configuration directory '/Users/cesar/.wine' > wine: Unhandled page fault on read access to 0x008cc65f at address > 0xffff0eb8 (thread 000b), starting debugger... > couldn't load main module (2) > Unhandled exception:

Hi, there I recently purchased a copy of bordeaux in order to try the dib engine (and pulse) in wine1.2 I would like to use this in already installed bottles. So I tried something like this: code: [export WINEDIB=ON] then (as an example) code:[/opt/bordeaux/bin/wine | env WINEPREFIX=~/.wine-test wine winecfg] This does create a wine bottle, but in this way the dib engine doesn't get loaded

2014-02-11 11:41 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: > (b) bisect. you can (almost) definitely restrict the bisect to > drivers/gpu/drm/nouveau. if you have additional computational power, i > would recommend looking into distcc for speeding up the compiles. it > may be interesting to also try 3.6.x since 3.7 received a pretty big > rewrite. but a git bisect is a

I'm confused by this: > > ... then you need to reset your bisect and use that "Release x.x.xx" as your first good bisect (wine-x.x.xx). This particular bisect output is just a version tag, meaning that no real code was changed (and so cannot have made your problem appear). All the "good" bisects you've set tells GIT that all that code is good, until wine-x.x.xx

I'm currently in the process of regression testing a bug (http://bugs.winehq.org/show_bug.cgi?id=19219). However, I ran into a problem that http://www.winehq.org/docs/winedev-guide/x1348 doesn't cover. Say a dev submits a series of patches that rely on each other for something, such as communications. While doing git bisect, some of those patches end up on opposite sides of the bisect.

OK, I'm trying to make regression test for ddraw. Here is exactly what I did: 1: git clone git://source.winehq.org/git/wine.git wine-git cd wine-git 2: git bisect start dlls/ddraw git bisect good wine-0.9.15 git bisect bad Now first test: CC="ccache gcc" ./configure ?verbose && make depend -j2 && make -j2 Compilation successful regression present, another run:

List: I have no familarity with this program. The following is from Bob. I have also asked Bob to install this program using the installation media provided by the producer of this program. Anyone else want to interceed and assist Bob with this problem? Thank you. James McKenzie -------- Original Message -------- Subject: Re: Deleting .wine as root Date: Sat, 31 Jul 2010 12:58:35 -0400

Hi, I have been trying to do a regression test between 1.1.10 and 1.1.12, as there seems to be a number of problems with the installation of the Macromedia suite (Dreamweaver, Fireworks, Flash). I think I have ccache installed. I think I have git OK. I run git bisect start ok, Then when I run git bisect good wine 1.1.10, I get: Bad rev input: wine 1.1.10. What am I doing wrong?

Forwarding to the list. Anyone experienced this? James McKenzie -------- Original Message -------- Subject: Re: Regsvr32 running through Gecko Date: Mon, 20 Sep 2010 09:06:55 -0700 (GMT-07:00) From: James Mckenzie <jjmckenzie51 at earthlink.net> Reply-To: James Mckenzie <jjmckenzie51 at earthlink.net> To: Jacek Caban <jacek at codeweavers.com> Jacek Caban<jacek at

Hi Reed, On 13 September 2013 00:35, reed kotler <rkotler at mips.com> wrote: > What are most people using to bisect svn or git in order to find llvm > regressions? Do you mean some script to use with "git bisect run"? I've not seen one; I suspect the simple cases are too easy to spot and the hard ones too diverse to be worth it > For example, something on Sunday

2014-02-16 19:55 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: > On Sun, Feb 16, 2014 at 10:17 AM, Rafa? Mi?ecki <zajec5 at gmail.com> wrote: >> 2014-02-11 11:41 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: >>> (b) bisect. you can (almost) definitely restrict the bisect to >>> drivers/gpu/drm/nouveau. if you have additional computational power, i

Hi, I need help to find the commit when a regression happened: http://bugs.winehq.org/show_bug.cgi?id=18436 I know git, and I can run git bisect just fine. Wine compiles (even if I have to patch version 1.0 since freetype changed). But when I try to install my application or run it using the built wine, I got a problem. the WINEPREFIX is an empty directory at the start, and when I run