similar to: Regression Testing Issue

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:

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

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

abb4 <wineforum-user at winehq.org> wrote: > >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 This is the KEY. There may be MORE THAN ONE BAD COMMIT.

Hi! I probably found regression in Wine. The problem is i don't know last stable release name (tag, version number) of Wine which don't have this regression. I carefully read about regressions here http://wiki.winehq.org/RegressionTesting Here i see a way to setup git tree somewhere between stable versions. It can be useful if i exactly know two adjacent (neighbour) stable version numbers

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

https://bugs.freedesktop.org/show_bug.cgi?id=101587 Bug ID: 101587 Summary: [BISECTED][REGRESSION] Nouveau kernel module (>4.10) on NVA8 renders the system unusable Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

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

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

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?

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'm following the WineGit instructions to try and discover why Money 2004 doesn't run with 0.9.12 or later. This is the first time I have tried to do regression testing, so I need some help. Is this the correct group to ask? I have installed git 1.1.4, copied the GIT repository to my PC, installed g++, yacc and bison, bisected the source tree and compiled. I then ran Money and

What are most people using to bisect svn or git in order to find llvm regressions? For example, something on Sunday made one test for mips16 fail and I was wondering if there is some simple script people already have for zeroing in on the change that made something not regress. Tia. Reed

Hello Ben, > Are you able to double-check that bisect? I'm not at all sure how > that particular commit could trigger the issue you're seeing. Some of > the others, certainly. It might be worth trying a couple of times > before marking something as "good", in case there's a timing aspect to > the problem. please CC me, otherwise I might not see your

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

On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: > > Some display stuff did change for 4.13 for GM20x+ boards. If it's not > too much trouble, a bisect would be pretty useful. Bisection seemingly went fine, but the result is odd. e98c58e55f68f8785aebfab1f8c9a03d8de0afe1 is the first bad commit -Mike

On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: > > OK, thanks. So in other words, a fairly standard desktop with a PCIe > board plugged in. No funny business. (Laptops can create a ton of > additional weirdness, which I assumed you had since you were talking > about STR.) Yup, garden variety deskside box. > My best guess is that gf119_head_vblank_put either has a bogus

When I try to run counterstrike, I get the following: fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub. dir: C:\Program Files\Steam\bin\ *.mix dir: C:\Program Files\Steam\bin\ *.asi dir: C:\Program Files\Steam\bin\ *.flt warning: Unknown nb_ctl request: 4 warning: Unknown nb_ctl request: 30 err:dscapture:widDsCreate DirectSoundCapture flag not set This sound

Hi! On v4.18-rc1, the mouse cursor is missing on my right monitor. Card is G98 [GeForce 8400 GS Rev. 2]. I have two monitors: one small landscape 1280x1024 on DVI-I-1 left, and one big 1600x1200 (1200x1600 portrait) on HDMI-1 right. Curiously, the cursor is missing not only with proper xrandr setup after logging in but even in mirrored mode at the lightdm greeter[1]. How is this even possible