> On 22 Feb 2016, at 11:21, Lars Schneider <larsxschneider@xxxxxxxxx> wrote: > > >> On 22 Feb 2016, at 11:12, Mehul Jain <mehul.jain2029@xxxxxxxxx> wrote: >> >> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy >> <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: >>> The simplest way to get back on track for you is probably to start over >>> with a fresh clone, or (warning: destructive operations): use git clean >>> to remove untracked files. >> >> Hello Matthieu, >> >> I followed your advise and cloned a fresh copy of git source code. >> After compiling it and running the test with " prove --timer --jobs 15 >> ./t[0-9]*.sh" command, I received tests failure. All these tests are >> regarding HTTP protocol being invoked like >> t5539-fetch-http-shallow.sh. >> >> I'm behind a proxy server which blocks all ports except 80 and 443. >> Also my .gitconfig file is properly configured for proxy. Can these >> tests failure be triggered because of proxy server? >> > > Hi Mehul, > > please try this: > https://github.com/git/git.github.io/commit/9754cb22aeacf37fe341c5b3fde88f2a79e0ea24 > Oops.. I am sorry. I should have read your email more closely. t5539 is not yet executed on Travis-CI... But it wouldn't be too hard to add ;-) Cheers, Lars-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html