Re: testsuite failures in mainline...
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:59
David Miller [off-list ref] writes:
I've been seeing this for I think a week or two, and I can't figure out if it's some local problem of mine. I even reran the testsuite with "PATH=$(pwd):$PATH" just in case it was picking up my existing 1.5.3.7 installation for some reason, but it still fails even in that case. Is the following a known issue?
No, you are the first to report it here. I do not push out the tip of 'master' and 'next' unless all tests pass in my primary repository on my private machine and in a repository under my k.org account, so you can at least assume all tests has passed for _some_ people. It of course does not guarantee there isn't timing related bugs I am not catching.
*** t3200-branch.sh ***
...
* FAIL 20: test tracking setup via config
git config branch.autosetupmerge true &&
git config remote.local.url . &&
git config remote.local.fetch refs/heads/*:refs/remotes/local/* &&
(git show-ref -q refs/remotes/local/master || git-fetch local) &&
git branch my3 local/master &&
test $(git config branch.my3.remote) = local &&
test $(git config branch.my3.merge) = refs/heads/masterWhen I can reproduce a breakage, in our tests, I'd run cd t && sh -x t3200-branch.sh -i -v (replace "t3200-*" with the failing test) and see which one of the steps chained with && is breaking first.