{"thread":{"id":"39205","subject":"[Test Failure] t5570 - not cloned","startedAt":"2015-05-01T15:04:48Z","lastAt":"2015-05-02T18:24:21Z","messageCount":2,"participants":["Randall S. Becker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"260340","messageId":"003901d08420$2b9fd7a0$82df86e0$@nexbridge.com","threadId":"39205","inReplyTo":null,"subject":"[Test Failure] t5570 - not cloned","fromName":"Randall S. Becker","fromEmail":"rsbecker@nexbridge.com","sentAt":"2015-05-01T15:04:48Z","receivedAt":"2015-05-01T15:04:48Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"Greetings - and asking for a bit of help resolving test failures.\n\nI'm having an issue with t5570 at 2.3.7 which seems to be a regression from\n2.3.3 (currently installed), but I cannot be sure. This test failed prior to\n2.3.0 in the box, worked from 2.3.0 to 2.3.3 - suggesting that it may be\nenvironmental, not actually in git. Making some assumptions, it looks like\nthe URL for the test repository is not correct and may depend on localhost\nresolving properly - which DNS does not do well on this box (outside my\ncontrol, we are multi-home, and localhost does not resolve to 127.0.0.1 or\n[::1]). Only t5570 #'s 3-5 fail and I found a strange message in the output\nof the test seemingly referring to a bad repo name. I would really\nappreciate some pointers on where to look next and how to go about resolving\nthis. I am happy to try to work through this on 2.4.0 if that would be more\nefficient for the team. Anything relating to git-daemon makes me nervous in\nterms of installing the code.\n\nPlatform is HP NonStop (Posix-esque environment):\n\nIn the test output:\n*** t5570-git-daemon.sh ***\n<snip>\nnot ok 3 - clone git repository\n#\n#               git clone \"$GIT_DAEMON_URL/repo.git\" clone &&\n#               test_cmp file clone/file\n#\nnot ok 4 - fetch changes via git protocol\n#\n#               echo content >>file &&\n#               git commit -a -m two &&\n#               git push public &&\n#               (cd clone && git pull) &&\n#               test_cmp file clone/file\n#\nnot ok 5 - remote detects correct HEAD\n#\n#               git push public master:other &&\n#               (cd clone &&\n#                git remote set-head -d origin &&\n#                git remote set-head -a origin &&\n\nAnd\n\n../git/t/trash directory.t5570-git-daemon: cat output\nfatal: remote error: repository not exported: /repo.git\n\nAdditional context: t0025, t0301, t3900, t9001, t9020 are not 100% but the\nissues are acceptable - we can discuss separately.\n\nCheers,\nRandall\n\n-- Brief whoami: NonStop&UNIX developer since approximately\nUNIX(421664400)/NonStop(211288444200000000)\n-- In my real life, I talk too much.\n"},{"id":"260436","messageId":"002601d08505$3645d020$a2d17060$@nexbridge.com","threadId":"39205","inReplyTo":"003901d08420$2b9fd7a0$82df86e0$@nexbridge.com","subject":"RE: [Test Failure] t5570 - not cloned","fromName":"Randall S. Becker","fromEmail":"rsbecker@nexbridge.com","sentAt":"2015-05-02T18:24:21Z","receivedAt":"2015-05-02T18:24:21Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On May 1, 2015 11:05 AM, I wrote, in my haste:\n> \n> Greetings - and asking for a bit of help resolving test failures.\n> \n> I'm having an issue with t5570 at 2.3.7 which seems to be a regression\nfrom\n> 2.3.3 (currently installed), but I cannot be sure. This test failed prior\nto\n> 2.3.0 in the box, worked from 2.3.0 to 2.3.3 - suggesting that it may be\n> environmental, not actually in git. Making some assumptions, it looks like\n> the URL for the test repository is not correct and may depend on localhost\n> resolving properly - which DNS does not do well on this box (outside my\n> control, we are multi-home, and localhost does not resolve to 127.0.0.1 or\n> [::1]). Only t5570 #'s 3-5 fail and I found a strange message in the\noutput\n> of the test seemingly referring to a bad repo name. I would really\n> appreciate some pointers on where to look next and how to go about\nresolving\n> this. I am happy to try to work through this on 2.4.0 if that would be\nmore\n> efficient for the team. Anything relating to git-daemon makes me nervous\nin\n> terms of installing the code.\n> \n> Platform is HP NonStop (Posix-esque environment):\n> \n> In the test output:\n> *** t5570-git-daemon.sh ***\n> <snip>\n> not ok 3 - clone git repository\n> #\n> #               git clone \"$GIT_DAEMON_URL/repo.git\" clone &&\n> #               test_cmp file clone/file\n> #\n> not ok 4 - fetch changes via git protocol\n> #\n> #               echo content >>file &&\n> #               git commit -a -m two &&\n> #               git push public &&\n> #               (cd clone && git pull) &&\n> #               test_cmp file clone/file\n> #\n> not ok 5 - remote detects correct HEAD\n> #\n> #               git push public master:other &&\n> #               (cd clone &&\n> #                git remote set-head -d origin &&\n> #                git remote set-head -a origin &&\n> \n> And\n> \n> ../git/t/trash directory.t5570-git-daemon: cat output\n> fatal: remote error: repository not exported: /repo.git\n> \n> Additional context: t0025, t0301, t3900, t9001, t9020 are not 100% but the\n> issues are acceptable - we can discuss separately.\n\nWe definitely have an issue with localhost. When forcing the resolver to\nreturn 127.0.0.1, we pass 1-16 then 17 fails as I expected to happen based\non my DNS futzing. Heads up that this test is not-surprisingly sensitive to\nDNS problems. My environment is still in a messy state where I can reproduce\nthe original problem so it might be a useful moment for me to find a way to\nmodify the test to harden it. Any suggestion on that score (as in where and\nroughly how you'd like it hardened)?\n\nCheers,\nRandall\n"}]}