similar to: Re: regression, troubles with setup git tree

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

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 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?

Based on the feedback so far, I propose that we call this discussion done -- we will not go with this zippered proposal, but will proceed with https://github.com/llvm-git-prototype/llvm/. On Thu, Nov 15, 2018 at 5:06 PM David Greene via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > What is the status

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

On 10/31/2018 03:02 PM, Justin Bogner wrote: > Tom Stellard <tstellar at redhat.com> writes: >>> On 10/31/2018 10:39 AM, Justin Bogner wrote: >>>> Tom Stellard <tstellar at redhat.com> writes: >>>>> On 10/31/2018 09:22 AM, Justin Bogner via llvm-dev wrote: >>>>>> Hi all, >>>>>> >>>>>> I've

Yes, I’m still trying to evaluate the migration script’s downsides as compared to the zipper approach’s downsides. Sorry that I got a little held up, but I have to balance evaluating this with getting other work done. I should have some feedback to a few of the responses on this thread next week. I really don’t think I can respond in a useful/productive way before I’ve finished these

Hi, > On Sep 7, 2016, at 10:30 AM, dag at cray.com wrote: > > Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> Right, we actually have a proposal to take what is in the current SVN >> repo here: http://llvm.org/svn/llvm-project/ and migrate this to a >> single repository. >> I was not sure if you were referring to this proposal

Hi!, latest git does not compile: rm at eurasia:~/swfdec/swfdec$ make make all-recursive make[1]: Entering directory `/home/rm/swfdec/swfdec' Making all in libswfdec make[2]: Entering directory `/home/rm/swfdec/swfdec/libswfdec' make[2]: *** No rule to make target `swfdec_as_scope.c', needed by `swfdec_asnative.h'. Stop. make[2]: Leaving directory

Hello, git bisect helped me today in tracking down a regression in LLVM/Clang. Because LLVM/Clang code is split across multiple git repositories, there were a few obstacles to overcome prior to using git bisect. I thought I would share them here, in the hope that they're useful for others. The main difficulty was to check out the version of clang and compiler-rt that would compile with 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

On 30 June 2016 at 05:14, Tim Northover <t.p.northover at gmail.com> wrote: >> That makes it fragile, and that’s why I disagree with your “90% done” assessment. >> What if the service behing the hook is down for a few days? > > In the long-term view, a pretty trivial catch-up script ought to be > able to synthesize a sane history after any amount of down-time. >

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 don't feel like I can unilaterally declare this topic closed, since there was an objection to that last time. But with no additional feedback after another week, I'd still really like to close this out, and start moving forward with the original plan, again... On Mon, Nov 26, 2018 at 2:28 PM James Y Knight <jyknight at google.com> wrote: > It's been a week and a half more

Hi, Thanks for starting this discussion Justin! On 10/31/18 5:22 PM, Justin Bogner via llvm-dev wrote: > Hi all, > > I've spent some time in the last couple of days trying to figure out how > to adopt the [LLVM git monorepo prototype] for an out of tree backend. > TLDR: I'm not convinced that this prototype is the right approach to > converting to the monorepo, and I

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:

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

On Jul 23, 2011, at 4:34 AM, Matthieu Moy wrote: > Chris Lattner <clattner at apple.com> writes: > >> I really do appreciate distributed VCS, but only as staging. >> Incremental development is crucial for the project and "take this git >> push with 100K of code" will never be acceptable. > > Incremental development is probably promoted by DVCS far

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

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