{"thread":{"id":"41445","subject":"GSoC 2016: Microproject","startedAt":"2016-02-19T08:59:03Z","lastAt":"2016-02-22T12:28:15Z","messageCount":18,"participants":["Mehul Jain","Matthieu Moy","Stefan Beller","Karthik Nayak","Duy Nguyen","Lars Schneider"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"278623","messageId":"CA+DCAeTAmUAciCx33ZHLKReHSy4K-dEeaKSb19qBcQc_U80UJA@mail.gmail.com","threadId":"41445","inReplyTo":null,"subject":"GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-19T08:59:03Z","receivedAt":"2016-02-19T08:59:03Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"Hello everyone,\n\nI'm Mehul Jain. I'm looking for participating in GSoC 2016.\n\nI've started work on a Microproject\" Teach git pull --rebase the\n--no-autostash\" option. While looking at Git's source code I have made\nfollowing observation: In the pull.c file\n1. git_config_get_bool( , ) search in the configuration key for the\nvalue of rebase.autostash, if found true then modify autostash's value\nto a non-zero number and thus making a stash to encounter the problem\nof dirty tree.\n2. Here if in command line a flag \"--no-autostash\" is given then we\ncan easily set the value of autostash = 0 and thus killing the process\nby die_on_unclean_work_tree(prefix).\nIs my observation is right?\n\nI'm new to open source projects and not much experienced at it. So\nplease correct/comment on any mistake that I made while trying to put\nmy point. I will also appreciate any comment/suggestion/criticism on\nmy observation.\n\nThanks\n"},{"id":"278667","messageId":"vpq37so26oz.fsf@anie.imag.fr","threadId":"41445","inReplyTo":"CA+DCAeTAmUAciCx33ZHLKReHSy4K-dEeaKSb19qBcQc_U80UJA@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-02-19T13:03:24Z","receivedAt":"2016-02-19T13:03:24Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Hi,\n\nThis is a double-post. You've posted almost the same message under the\ntitle \"GSoC 2016\". Nothing serious, but attention to details is\nimportant if you want to give a good image of yourself.\n\nMehul Jain writes:\n\n> Hello everyone,\n>\n> I'm Mehul Jain. I'm looking for participating in GSoC 2016.\n\nNote that we are just submitting our application, but have no guarantee\nthat the Git organization will be accepted for this year's GSoC.\n\n> I've started work on a Microproject\" Teach git pull --rebase the\n> --no-autostash\" option. While looking at Git's source code I have made\n> following observation: In the pull.c file\n> 1. git_config_get_bool( , ) search in the configuration key for the\n> value of rebase.autostash, if found true then modify autostash's value\n> to a non-zero number and thus making a stash to encounter the problem\n> of dirty tree.\n> 2. Here if in command line a flag \"--no-autostash\" is given then we\n> can easily set the value of autostash = 0 and thus killing the process\n> by die_on_unclean_work_tree(prefix).\n> Is my observation is right?\n\nI don't have all the code in mind, but I think it is. In this situation,\nyou always end up with a variable telling Git what to do (I guess,\nautostash here), and this variable is set according to the configuration\nand the command-line.\n\nYou should be careful about the precedence: command-line should override\nthe configuration. And the default behavior should be used if neither\nthe command-line nor the configuration specified otherwise.\n\nTo get an example, you can pick any pair (command-line option, config)\nthat work together, find the code implementing it and blame to find the\ncorresponding commit.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"278676","messageId":"CA+DCAeQLJnvNFdSobDNOGVaHbDRnRy4vm9_4SB+Bw+5N5QMKHA@mail.gmail.com","threadId":"41445","inReplyTo":"vpq37so26oz.fsf@anie.imag.fr","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-19T17:39:26Z","receivedAt":"2016-02-19T17:39:26Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy\n wrote:\n> Hi,\n>\n> This is a double-post. You've posted almost the same message under the\n> title \"GSoC 2016\". Nothing serious, but attention to details is\n> important if you want to give a good image of yourself.\n\nI'm sorry of this kind of behavior. It was due to a misunderstanding by my side.\n\n> I don't have all the code in mind, but I think it is. In this situation,\n> you always end up with a variable telling Git what to do (I guess,\n> autostash here), and this variable is set according to the configuration\n> and the command-line.\n>\n> You should be careful about the precedence: command-line should override\n> the configuration. And the default behavior should be used if neither\n> the command-line nor the configuration specified otherwise.\n\nThanks for the suggestion.\nI've started the work on patch and did the change in the code which\nwere necessary for Microproject. I have run the test by using \"make\",\nand there was no failure of any test.\nI've a doubt regarding tests. Here as \"git pull\" will now understand\nthe argument that \"--[no-]autostash\" means \"rebase.autostash\" should\nbe set false for current execution of command \"git pull --rebase\". So\ndo I have to write a test for this new option?\n\nMehul Jain\n"},{"id":"278678","messageId":"CAGZ79kbdTFui5Zxmt0+BrgOzxTFsN2n-XZiJBNj4QFD3HPRpBQ@mail.gmail.com","threadId":"41445","inReplyTo":"CA+DCAeQLJnvNFdSobDNOGVaHbDRnRy4vm9_4SB+Bw+5N5QMKHA@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2016-02-19T17:50:40Z","receivedAt":"2016-02-19T17:50:40Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Fri, Feb 19, 2016 at 9:39 AM, Mehul Jain wrote:\n> On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy\n> wrote:\n>> Hi,\n>>\n>> This is a double-post. You've posted almost the same message under the\n>> title \"GSoC 2016\". Nothing serious, but attention to details is\n>> important if you want to give a good image of yourself.\n>\n> I'm sorry of this kind of behavior. It was due to a misunderstanding by my side.\n>\n>> I don't have all the code in mind, but I think it is. In this situation,\n>> you always end up with a variable telling Git what to do (I guess,\n>> autostash here), and this variable is set according to the configuration\n>> and the command-line.\n>>\n>> You should be careful about the precedence: command-line should override\n>> the configuration. And the default behavior should be used if neither\n>> the command-line nor the configuration specified otherwise.\n>\n> Thanks for the suggestion.\n> I've started the work on patch and did the change in the code which\n> were necessary for Microproject. I have run the test by using \"make\",\n> and there was no failure of any test.\n> I've a doubt regarding tests. Here as \"git pull\" will now understand\n> the argument that \"--[no-]autostash\" means \"rebase.autostash\" should\n> be set false for current execution of command \"git pull --rebase\". So\n> do I have to write a test for this new option?\n>\n\nYes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right\nplace as judging from the file name of the tests.\n\nThanks,\nStefan\n\n> Mehul Jain\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n"},{"id":"278689","messageId":"CA+DCAeSH4S9F-1Z90cxbNNJu-6KTuOB_Jro9UdYnTAQGx3xzOg@mail.gmail.com","threadId":"41445","inReplyTo":"CAGZ79kbdTFui5Zxmt0+BrgOzxTFsN2n-XZiJBNj4QFD3HPRpBQ@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-19T18:32:35Z","receivedAt":"2016-02-19T18:32:35Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote:\n> Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right\n> place as judging from the file name of the tests.\n\nThanks for specifying the files. I think t/t5520-pull.sh line 258 will\nbe the best place to write test for this case.\n\nMehul Jain\n"},{"id":"278735","messageId":"CA+DCAeRTtECCZSAPYUe2=AoQEvc6LRG1B+qYCCj9C6_nyUJrhw@mail.gmail.com","threadId":"41445","inReplyTo":"CAGZ79kbdTFui5Zxmt0+BrgOzxTFsN2n-XZiJBNj4QFD3HPRpBQ@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-20T14:43:40Z","receivedAt":"2016-02-20T14:43:40Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"Hello,\n\nI faced the following problem when I tested master branch. Here I have\nmade no commits to master branch.\n\n*** t5539-fetch-http-shallow.sh ***\nok 1 - setup shallow clone\nnot ok 2 - clone http repository\n#\n# git clone --bare --no-local shallow \"$HTTPD_DOCUMENT_ROOT_PATH/repo.git\" &&\n# git clone $HTTPD_URL/smart/repo.git clone &&\n# (\n# cd clone &&\n# git fsck &&\n# git log --format=%s origin/master >actual &&\n# cat <expect &&\n# 7\n# 6\n# 5\n# 4\n# 3\n# EOF\n# test_cmp expect actual\n# )\n#\nnot ok 3 - no shallow lines after receiving ACK ready\n#\n# (\n# cd shallow &&\n# test_tick &&\n# for i in $(test_seq 15)\n# do\n# git checkout --orphan unrelated$i &&\n# test_commit unrelated$i &&\n# git push -q \"$HTTPD_DOCUMENT_ROOT_PATH/repo.git\" \\\n# refs/heads/unrelated$i:refs/heads/unrelated$i &&\n# git push -q ../clone/.git \\\n# refs/heads/unrelated$i:refs/heads/unrelated$i ||\n# exit 1\n# done &&\n# git checkout master &&\n# test_commit new &&\n# git push \"$HTTPD_DOCUMENT_ROOT_PATH/repo.git\" master\n# ) &&\n# (\n# cd clone &&\n# git checkout --orphan newnew &&\n# test_commit new-too &&\n# GIT_TRACE_PACKET=\"$TRASH_DIRECTORY/trace\" git fetch --depth=2 &&\n# grep \"fetch-pack< ACK .* ready\" ../trace &&\n# ! grep \"fetch-pack> done\" ../trace\n# )\n#\n# failed 2 among 3 test(s)\n1..3\nmake[1]: *** [t5539-fetch-http-shallow.sh] Error 1\nmake[1]: Leaving directory `/home/mj/git/t'\nmake: *** [test] Error 2\n\nIs this test failure usual with linux based system or just happened with me.\nI'm running Ubuntu 14.04.\n\nthanks,\nMehul Jain\n\nOn Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote:\n> On Fri, Feb 19, 2016 at 9:39 AM, Mehul Jain wrote:\n>> On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy\n>> wrote:\n>>> Hi,\n>>>\n>>> This is a double-post. You've posted almost the same message under the\n>>> title \"GSoC 2016\". Nothing serious, but attention to details is\n>>> important if you want to give a good image of yourself.\n>>\n>> I'm sorry of this kind of behavior. It was due to a misunderstanding by my side.\n>>\n>>> I don't have all the code in mind, but I think it is. In this situation,\n>>> you always end up with a variable telling Git what to do (I guess,\n>>> autostash here), and this variable is set according to the configuration\n>>> and the command-line.\n>>>\n>>> You should be careful about the precedence: command-line should override\n>>> the configuration. And the default behavior should be used if neither\n>>> the command-line nor the configuration specified otherwise.\n>>\n>> Thanks for the suggestion.\n>> I've started the work on patch and did the change in the code which\n>> were necessary for Microproject. I have run the test by using \"make\",\n>> and there was no failure of any test.\n>> I've a doubt regarding tests. Here as \"git pull\" will now understand\n>> the argument that \"--[no-]autostash\" means \"rebase.autostash\" should\n>> be set false for current execution of command \"git pull --rebase\". So\n>> do I have to write a test for this new option?\n>>\n>\n> Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right\n> place as judging from the file name of the tests.\n>\n> Thanks,\n> Stefan\n>\n>> Mehul Jain\n>> --\n>> To unsubscribe from this list: send the line \"unsubscribe git\" in\n>> the body of a message to majordomo@vger.kernel.org\n>> More majordomo info at http://vger.kernel.org/majordomo-info.html\n"},{"id":"278846","messageId":"vpq8u2er7ae.fsf@anie.imag.fr","threadId":"41445","inReplyTo":"CA+DCAeRTtECCZSAPYUe2=AoQEvc6LRG1B+qYCCj9C6_nyUJrhw@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-02-21T04:55:53Z","receivedAt":"2016-02-21T04:55:53Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Please, don't top-post on this list.\n\nMehul Jain writes:\n\n> Hello,\n>\n> I faced the following problem when I tested master branch. Here I have\n> made no commits to master branch.\n\nAre you sure that 1) you have no uncommitted change and 2) you have\ncompiled what you have in your tree?\n\n> Is this test failure usual with linux based system or just happened with me.\n\nAll tests are supposed to pass. You can see the result of the Travis-CI\nbuilds there:\n\n https://travis-ci.org/git/git/branches\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"278763","messageId":"CA+DCAeSpN+OSJ85yyqq9ONzfubh=coMd7FTct5OkEnLvhMm2tw@mail.gmail.com","threadId":"41445","inReplyTo":"CAGZ79kbdTFui5Zxmt0+BrgOzxTFsN2n-XZiJBNj4QFD3HPRpBQ@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-21T16:02:37Z","receivedAt":"2016-02-21T16:02:37Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote:\n> Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right\n> place as judging from the file name of the tests.\n\nI checked out both of the files and made following observations -\n\n1) As I'm going to add an option for \"git pull --rebase\"; tests should\nbe added for following commands in t/t5521-pull-options.sh\n a) git pull --rebase --[no-]autostash\n b) git pull -v --rebase --[no-]autostash\n c) git pull -q --rebase --[no-]autostash\n\n2) Also test for \"pull --rebase --[no-]autostash fails with dirty\nworking tree and rebase.autostash set\" should be added to\nt/t5520-pull.sh.\n\nHave I made the right observation?\n\nThanks,\nMehul Jain\n"},{"id":"278766","messageId":"CA+DCAeQWeUodaBtHOdzGB3RTZTQ672ZUSV-=eh-nA+8Bvn4gxw@mail.gmail.com","threadId":"41445","inReplyTo":"vpq8u2er7ae.fsf@anie.imag.fr","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-21T16:04:18Z","receivedAt":"2016-02-21T16:04:18Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Sun, Feb 21, 2016 at 10:25 AM, Matthieu Moy\n wrote:\n> Please, don't top-post on this list.\n\nI apologize for top-posting on the list.\n\n> Are you sure that 1) you have no uncommitted change and 2) you have\n> compiled what you have in your tree?\n\n1) Yes, I have no uncommited change in the branch(master).\n2) Yes, I compiled before testing.\n\nEarlier when I was testing the master branch on my pc, I used \"make\"\nin \\t directory, which lead to failure of test #2, #3 in\nt5539-fetch-http-shallow.sh .\nAfterwards I switched to sudo mode and ran the make command again.\nThis time all test of t5539-fetch-http-shallow.sh passed, but test\n#32 of file t7300-clean.sh failed. To crosscheck, I ran \" sudo sh\n./t7300-clean.sh -v --run='1-32' \" which gave the following error\nmessage -\n\nSkipping repository baz/boo\nSkipping repository foo/\nRemoving possible_sub1/\nSkipping repository repo/\nSkipping repository sub2/\nRemoving to_clean/\nFile possible_sub1/.git doesn't exist.\nnot ok 32 - should avoid cleaning possible submodules\n#\n# rm -fr to_clean possible_sub1 &&\n# mkdir to_clean possible_sub1 &&\n# test_when_finished \"rm -rf possible_sub*\" &&\n# echo \"gitdir: foo\" >possible_sub1/.git &&\n# >possible_sub1/hello.world &&\n# chmod 0 possible_sub1/.git &&\n# >to_clean/should_clean.this &&\n# git clean -f -d &&\n# test_path_is_file possible_sub1/.git &&\n# test_path_is_file possible_sub1/hello.world &&\n# test_path_is_missing to_clean\n#\n\nI haven't made any commits/changes in the master branch. Can you\nplease suggest where things are going wrong.\n\nThanks\nMehul Jain\n"},{"id":"278775","messageId":"vpq1t85rj44.fsf@anie.imag.fr","threadId":"41445","inReplyTo":"CA+DCAeQWeUodaBtHOdzGB3RTZTQ672ZUSV-=eh-nA+8Bvn4gxw@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-02-21T18:52:43Z","receivedAt":"2016-02-21T18:52:43Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Mehul Jain writes:\n\n> Earlier when I was testing the master branch on my pc, I used \"make\"\n> in \\t directory, which lead to failure of test #2, #3 in\n> t5539-fetch-http-shallow.sh .\n> Afterwards I switched to sudo mode and ran the make command again.\n\nNever ever do that. Your git source tree should be within your $HOME\ndirectory, and you should never run any command as root that creates\nfiles within your $HOME dir. If you do that, you'll end up having files\nbelonging to root within other directories, you won't have write\npermission on these files. Then, anything can go wrong because any\nattempt to write to these files will fail.\n\nThe simplest way to get back on track for you is probably to start over\nwith a fresh clone, or (warning: destructive operations): use git clean\nto remove untracked files.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"278844","messageId":"CAOLa=ZQqyfGDOVr=nxKbuZXJw2rsCu0KbomG+tuRkeS+R9xzFw@mail.gmail.com","threadId":"41445","inReplyTo":"vpq1t85rj44.fsf@anie.imag.fr","subject":"Re: GSoC 2016: Microproject","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2016-02-22T08:10:37Z","receivedAt":"2016-02-22T08:10:37Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy\n wrote:\n> Mehul Jain writes:\n>\n>> Earlier when I was testing the master branch on my pc, I used \"make\"\n>> in \\t directory, which lead to failure of test #2, #3 in\n>> t5539-fetch-http-shallow.sh .\n>> Afterwards I switched to sudo mode and ran the make command again.\n>\n> Never ever do that. Your git source tree should be within your $HOME\n> directory, and you should never run any command as root that creates\n> files within your $HOME dir. If you do that, you'll end up having files\n> belonging to root within other directories, you won't have write\n> permission on these files. Then, anything can go wrong because any\n> attempt to write to these files will fail.\n>\n> The simplest way to get back on track for you is probably to start over\n> with a fresh clone, or (warning: destructive operations): use git clean\n> to remove untracked files.\n>\n\nI think a 'sudo git clean' outta be enough. But the main point to take away is\nnot using 'make' with 'sudo' like you mentioned.\n\n-- \nRegards,\nKarthik Nayak\n"},{"id":"278852","messageId":"CA+DCAeQGPqZvvn5RSA0UweM4sQLat-2OPo4BdEDyvUbq+eLi=w@mail.gmail.com","threadId":"41445","inReplyTo":"vpq1t85rj44.fsf@anie.imag.fr","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-22T10:12:11Z","receivedAt":"2016-02-22T10:12:11Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy\n wrote:\n> The simplest way to get back on track for you is probably to start over\n> with a fresh clone, or (warning: destructive operations): use git clean\n> to remove untracked files.\n\nHello Matthieu,\n\nI followed your advise and cloned a fresh copy of git source code.\nAfter compiling it and running the test with \" prove --timer --jobs 15\n./t[0-9]*.sh\" command, I received tests failure. All these tests are\nregarding HTTP protocol being invoked like\nt5539-fetch-http-shallow.sh.\n\nI'm behind a proxy server which blocks all ports except 80 and 443.\nAlso my .gitconfig file is properly configured for proxy. Can these\ntests failure be triggered because of proxy server?\n\nThanks,\nMehul Jain\n"},{"id":"278853","messageId":"CACsJy8BKko=esR5Q3dsq=Z-pdX1EtocJr25tH4Fn+E-pOns=_Q@mail.gmail.com","threadId":"41445","inReplyTo":"CA+DCAeQGPqZvvn5RSA0UweM4sQLat-2OPo4BdEDyvUbq+eLi=w@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2016-02-22T10:20:35Z","receivedAt":"2016-02-22T10:20:35Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Feb 22, 2016 at 5:12 PM, Mehul Jain wrote:\n> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy\n> wrote:\n>> The simplest way to get back on track for you is probably to start over\n>> with a fresh clone, or (warning: destructive operations): use git clean\n>> to remove untracked files.\n>\n> Hello Matthieu,\n>\n> I followed your advise and cloned a fresh copy of git source code.\n> After compiling it and running the test with \" prove --timer --jobs 15\n> ./t[0-9]*.sh\" command, I received tests failure. All these tests are\n> regarding HTTP protocol being invoked like\n> t5539-fetch-http-shallow.sh.\n\nYou may have an http server installed but not suitable for these\ntests. Try running one test file alone with -v -i, e.g.\n./t5539-fetch-http-shallow.sh -v -i and post the output.\n\n> I'm behind a proxy server which blocks all ports except 80 and 443.\n> Also my .gitconfig file is properly configured for proxy. Can these\n> tests failure be triggered because of proxy server?\n\nNo. HTTP server will be run locally on your machine and serve all the tests.\n-- \nDuy\n"},{"id":"278854","messageId":"5B6C5271-FC9E-409E-9410-CE699499901D@gmail.com","threadId":"41445","inReplyTo":"CA+DCAeQGPqZvvn5RSA0UweM4sQLat-2OPo4BdEDyvUbq+eLi=w@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-02-22T10:21:33Z","receivedAt":"2016-02-22T10:21:33Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 22 Feb 2016, at 11:12, Mehul Jain wrote:\n> \n> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy\n> wrote:\n>> The simplest way to get back on track for you is probably to start over\n>> with a fresh clone, or (warning: destructive operations): use git clean\n>> to remove untracked files.\n> \n> Hello Matthieu,\n> \n> I followed your advise and cloned a fresh copy of git source code.\n> After compiling it and running the test with \" prove --timer --jobs 15\n> ./t[0-9]*.sh\" command, I received tests failure. All these tests are\n> regarding HTTP protocol being invoked like\n> t5539-fetch-http-shallow.sh.\n> \n> I'm behind a proxy server which blocks all ports except 80 and 443.\n> Also my .gitconfig file is properly configured for proxy. Can these\n> tests failure be triggered because of proxy server?\n> \n\nHi Mehul,\n\nplease try this:\nhttps://github.com/git/git.github.io/commit/9754cb22aeacf37fe341c5b3fde88f2a79e0ea24\n\nCheers,\nLars"},{"id":"278856","messageId":"CA+DCAeQADoW-r5ppDNXVBj0=16FXKi=3pedAzhRuCD9uDJz_YQ@mail.gmail.com","threadId":"41445","inReplyTo":"CACsJy8BKko=esR5Q3dsq=Z-pdX1EtocJr25tH4Fn+E-pOns=_Q@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-22T10:30:11Z","receivedAt":"2016-02-22T10:30:11Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Mon, Feb 22, 2016 at 3:50 PM, Duy Nguyen wrote:\n> You may have an http server installed but not suitable for these\n> tests. Try running one test file alone with -v -i, e.g.\n> ./t5539-fetch-http-shallow.sh -v -i and post the output.\n\nHere's the output :-\n\nexpecting success:\n git clone --bare --no-local shallow \"$HTTPD_DOCUMENT_ROOT_PATH/repo.git\" &&\n git clone $HTTPD_URL/smart/repo.git clone &&\n (\n cd clone &&\n git fsck &&\n git log --format=%s origin/master >actual &&\n cat <expect &&\n7\n6\n5\n4\n3\nEOF\n test_cmp expect actual\n )\n\nCloning into bare repository '/home/mj/git/t/trash\ndirectory.t5539-fetch-http-shallow/httpd/www/repo.git'...\nremote: Counting objects: 15, done.\nremote: Compressing objects: 100% (5/5), done.\nremote: Total 15 (delta 0), reused 15 (delta 0)\nReceiving objects: 100% (15/15), done.\nChecking connectivity... done.\nCloning into 'clone'...\nfatal: unable to access 'http://127.0.0.1:5539/smart/repo.git/': The\nrequested URL returned error: 403\nnot ok 2 - clone http repository\n#\n# git clone --bare --no-local shallow\n\"$HTTPD_DOCUMENT_ROOT_PATH/repo.git\" &&\n# git clone $HTTPD_URL/smart/repo.git clone &&\n# (\n# cd clone &&\n# git fsck &&\n# git log --format=%s origin/master >actual &&\n# cat <expect &&\n# 7\n# 6\n# 5\n# 4\n# 3\n# EOF\n# test_cmp expect actual\n# )\n#\n"},{"id":"278857","messageId":"9D5C632B-0F4C-482A-9A05-056B3F878B79@gmail.com","threadId":"41445","inReplyTo":"5B6C5271-FC9E-409E-9410-CE699499901D@gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-02-22T10:30:31Z","receivedAt":"2016-02-22T10:30:31Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 22 Feb 2016, at 11:21, Lars Schneider wrote:\n> \n> \n>> On 22 Feb 2016, at 11:12, Mehul Jain wrote:\n>> \n>> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy\n>> wrote:\n>>> The simplest way to get back on track for you is probably to start over\n>>> with a fresh clone, or (warning: destructive operations): use git clean\n>>> to remove untracked files.\n>> \n>> Hello Matthieu,\n>> \n>> I followed your advise and cloned a fresh copy of git source code.\n>> After compiling it and running the test with \" prove --timer --jobs 15\n>> ./t[0-9]*.sh\" command, I received tests failure. All these tests are\n>> regarding HTTP protocol being invoked like\n>> t5539-fetch-http-shallow.sh.\n>> \n>> I'm behind a proxy server which blocks all ports except 80 and 443.\n>> Also my .gitconfig file is properly configured for proxy. Can these\n>> tests failure be triggered because of proxy server?\n>> \n> \n> Hi Mehul,\n> \n> please try this:\n> https://github.com/git/git.github.io/commit/9754cb22aeacf37fe341c5b3fde88f2a79e0ea24\n> \nOops.. I am sorry. I should have read your email more closely. t5539 is not yet executed on Travis-CI...\nBut it wouldn't be too hard to add ;-)\n\nCheers,\nLars"},{"id":"278859","messageId":"CACsJy8B7m7PWY-RJ2pb3fAP6ZKz167Xzbby9Lo44gfDX9w7NPg@mail.gmail.com","threadId":"41445","inReplyTo":"CA+DCAeQADoW-r5ppDNXVBj0=16FXKi=3pedAzhRuCD9uDJz_YQ@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2016-02-22T11:21:22Z","receivedAt":"2016-02-22T11:21:22Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Feb 22, 2016 at 5:30 PM, Mehul Jain wrote:\n> On Mon, Feb 22, 2016 at 3:50 PM, Duy Nguyen wrote:\n>> You may have an http server installed but not suitable for these\n>> tests. Try running one test file alone with -v -i, e.g.\n>> ./t5539-fetch-http-shallow.sh -v -i and post the output.\n>\n> Here's the output :-\n>\n> expecting success:\n> git clone --bare --no-local shallow \"$HTTPD_DOCUMENT_ROOT_PATH/repo.git\" &&\n> git clone $HTTPD_URL/smart/repo.git clone &&\n> (\n> cd clone &&\n> git fsck &&\n> git log --format=%s origin/master >actual &&\n> cat <expect &&\n> 7\n> 6\n> 5\n> 4\n> 3\n> EOF\n> test_cmp expect actual\n> )\n>\n> Cloning into bare repository '/home/mj/git/t/trash\n> directory.t5539-fetch-http-shallow/httpd/www/repo.git'...\n> remote: Counting objects: 15, done.\n> remote: Compressing objects: 100% (5/5), done.\n> remote: Total 15 (delta 0), reused 15 (delta 0)\n> Receiving objects: 100% (15/15), done.\n> Checking connectivity... done.\n> Cloning into 'clone'...\n> fatal: unable to access 'http://127.0.0.1:5539/smart/repo.git/': The\n> requested URL returned error: 403\n\nOK server is up but very likely misconfigured. If you have experience\nwith http server before (I think this is apache), then you can dig in\nt/lib-httpd.sh, study how the server is configured and try to fix it.\n\nAlternatively, you can smiply skip http tests by setting environment\nvariable GIT_TEST_HTTPD to false before running the tests.\n-- \nDuy\n"},{"id":"278877","messageId":"CA+DCAeTYwfKy_S-5uy=BKNP5J3sa2+wMrpZEQZAikROmvOy1vw@mail.gmail.com","threadId":"41445","inReplyTo":"CACsJy8B7m7PWY-RJ2pb3fAP6ZKz167Xzbby9Lo44gfDX9w7NPg@mail.gmail.com","subject":"Re: GSoC 2016: Microproject","fromName":"Mehul Jain","fromEmail":"mehul.jain2029@gmail.com","sentAt":"2016-02-22T12:28:15Z","receivedAt":"2016-02-22T12:28:15Z","isPatch":false,"sender":{"key":"mehul.jain2029@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14936539?v=4"},"body":"On Mon, Feb 22, 2016 at 4:51 PM, Duy Nguyen wrote:\n> OK server is up but very likely misconfigured. If you have experience\n> with http server before (I think this is apache), then you can dig in\n> t/lib-httpd.sh, study how the server is configured and try to fix it.\n\nThanks Duy. :) All tests passed. I configured apache server to listen\nto the ports tests were trying to access.\n\nThanks Lars. I tested on Traivs-CI, worked fine. :)\n\nMehul Jain\n"}]}