Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From: "Junio C Hamano" Sent: Thursday, February 16, 2017 12:20 AM "Philip Oakley" writes: It may even be worth 'splitting' the pu branch sequence into the existing pu (with merges from series that are selected as reasonable), and then a pr branch

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

"Philip Oakley" writes: > For an integrator, or especially a CI tool, simply checking the second > parents of each topic merge (post fail) should at least indicate if > the basics of the feature actually passed the tests, though it doesn't > check for interaction issues.

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

"Philip Oakley" writes: > It may even be worth 'splitting' the pu branch sequence into the > existing pu (with merges from series that are selected as reasonable), > and then a pr branch (public review?) on top of that holding the rest > of the series that have been

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From: "Johannes Schindelin" Hi Philip, On Tue, 14 Feb 2017, Philip Oakley wrote: From: "Christian Couder" > On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano > wrote: > > Johannes Schindelin

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

[sorry for the repeated emails - I'd prepared it off line, and then suffered a number of auto send actions] From: "Junio C Hamano" "Philip Oakley" writes: In the next..pu case the abstraction is in the other direction, we have potentially multiple

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From: "Junio C Hamano" "Philip Oakley" writes: There are also a few ideas at the SO answers: http://stackoverflow.com/a/5652323/717355 I vaguely recall that I saw somebody said the same "mark tips of topics as good" on the list and answered with why

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From: "Junio C Hamano" "Philip Oakley" writes: There are also a few ideas at the SO answers: http://stackoverflow.com/a/5652323/717355 I vaguely recall that I saw somebody said the same "mark tips of topics as good" on the list and answered with why

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

"Philip Oakley" writes: > In the next..pu case the abstraction is in the other direction, we > have potentially multiple points of infection (from feature branches), > and a broad test (the whole test suite). In this case I believe we > would like to investigate initially

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From: "Junio C Hamano" "Philip Oakley" writes: There are also a few ideas at the SO answers: http://stackoverflow.com/a/5652323/717355 I vaguely recall that I saw somebody said the same "mark tips of topics as good" on the list and answered with why

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

Hi Philip, On Tue, 14 Feb 2017, Philip Oakley wrote: > From: "Christian Couder" > > On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano > > wrote: > > > Johannes Schindelin writes: > > > > > > > On Mon, 13 Feb 2017, Junio

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

Hi Christian, On Wed, 15 Feb 2017, Christian Couder wrote: > On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano > wrote: > > > Probably a less resource intensive approach is to find the tips of the > > topics not in 'next' but in 'pu' and test them. That would give you > >

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

"Philip Oakley" writes: > There are also a few ideas at the SO answers: > http://stackoverflow.com/a/5652323/717355 I vaguely recall that I saw somebody said the same "mark tips of topics as good" on the list and answered with why it does not quite work, though.

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From: "Christian Couder" On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano wrote: Johannes Schindelin writes: On Mon, 13 Feb 2017, Junio C Hamano wrote: Johannes Schindelin writes: >

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

Christian Couder writes: > By the way it should not be very difficult as a patch to do this and > more was proposed a long time ago: > > https://public-inbox.org/git/4d3cddf9.6080...@intel.com/ Thanks for a link. The one I found most interesting in the thread is by

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano wrote: > Johannes Schindelin writes: > >> On Mon, 13 Feb 2017, Junio C Hamano wrote: >> >>> Johannes Schindelin writes: >>> >>> > That is why I taught the Git for Windows

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

Johannes Schindelin writes: > On Mon, 13 Feb 2017, Junio C Hamano wrote: > >> Johannes Schindelin writes: >> >> > That is why I taught the Git for Windows CI job that tests the four >> > upstream Git integration branches to *also* bisect

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

Hi, On Mon, 13 Feb 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > That is why I taught the Git for Windows CI job that tests the four > > upstream Git integration branches to *also* bisect test breakages and > > then upload comments to the

Re: Continuous Testing of Git on Windows

Johannes Schindelin writes: > That is why I taught the Git for Windows CI job that tests the four > upstream Git integration branches to *also* bisect test breakages and then > upload comments to the identified commit on GitHub Good. I do not think it is useful to

Continuous Testing of Git on Windows

Hi team, at the GitMerge conference, I heard a couple of times "I do not bother reporting bugs in `pu` or `next` on MacOSX and Windows anymore, only Linux seems to be truly supported" or some variation thereof. This is a strong indicator that we have some room for improvement here. Active