{"thread":{"id":"46644","subject":"t5551 hangs ?","startedAt":"2017-08-22T05:11:06Z","lastAt":"2017-08-22T14:51:04Z","messageCount":4,"participants":["Torsten Bögershausen","Santiago Torres"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"326921","messageId":"20170822051059.GA26331@tor.lan","threadId":"46644","inReplyTo":null,"subject":"t5551 hangs ?","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2017-08-22T05:10:59Z","receivedAt":"2017-08-22T05:11:06Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"Hej,\nI found 2 threads about hanging t5551, one in 2016, and one question\nfrom Junio somewhen in 2017.\nI have it reproducable here:\n- Debian 8, 64 bit\n- SSD\n- Half-modern processor ;-)\n\nThe last thing I can see is:\nok 29 - test allowanysha1inwant with unreachable\n-----------\nA simplified ps -ef shows:\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/usr/sbin/apache2 -d /home/blalbla/t/trash directory.t5551-http-fetch-smart/httpd -f /home/blalbla/t/lib-httpd/apache.conf -c Listen 127.0.0.1:5551 -k start\n/home/blalbla/git -C too-many-refs fetch -q --tags\n/home/blalbla/git-remote-http origin http://127.0.0.1:5551/smart/repo.git\n-------------\nThe tests passes on another box (real old laptop, spinning disk)\n\nAnything that can be done to debug it ?\n\n\n"},{"id":"326922","messageId":"20170822052625.wzlhckjm6gwr2q6f@LykOS.localdomain","threadId":"46644","inReplyTo":"20170822051059.GA26331@tor.lan","subject":"Re: t5551 hangs ?","fromName":"Santiago Torres","fromEmail":"santiago@nyu.edu","sentAt":"2017-08-22T05:26:25Z","receivedAt":"2017-08-22T05:26:16Z","isPatch":false,"sender":{"key":"santiago@nyu.edu","avatar":"https://avatars.githubusercontent.com/u/3579933?v=4"},"body":"Hello, Torsten. \n\nOn Tue, Aug 22, 2017 at 07:10:59AM +0200, Torsten Bögershausen wrote:\n> Hej,\n> I found 2 threads about hanging t5551, one in 2016, and one question\n> from Junio somewhen in 2017.\n> I have it reproducable here:\n> - Debian 8, 64 bit\n> - SSD\n> - Half-modern processor ;-)\n\nI don't think the SSD/regular disk have anything to do with it. \n\n- Are you running tests concurrently? (e.g., with -j x)\n- What happens if you run the test individually (i.e., cd t and\n  ./t5551...)\n- You probably want to see the version of apache this is running/etc.\n- What happens if you kill the apache processes? \n\nI can't reproduce on my side, but let me see if I can dig a little into\nit.\n\nCheers!\n-Santiago.\n"},{"id":"326928","messageId":"20170822144357.GA5304@tor.lan","threadId":"46644","inReplyTo":"20170822052625.wzlhckjm6gwr2q6f@LykOS.localdomain","subject":"Re: t5551 hangs ?","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2017-08-22T14:43:57Z","receivedAt":"2017-08-22T14:44:27Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Tue, Aug 22, 2017 at 01:26:25AM -0400, Santiago Torres wrote:\n> Hello, Torsten. \n> \n> On Tue, Aug 22, 2017 at 07:10:59AM +0200, Torsten Bögershausen wrote:\n> > Hej,\n> > I found 2 threads about hanging t5551, one in 2016, and one question\n> > from Junio somewhen in 2017.\n> > I have it reproducable here:\n> > - Debian 8, 64 bit\n> > - SSD\n> > - Half-modern processor ;-)\n> \n> I don't think the SSD/regular disk have anything to do with it. \n> \n> - Are you running tests concurrently? (e.g., with -j x)\n> - What happens if you run the test individually (i.e., cd t and\n>   ./t5551...)\n\nNo concurrency.\nThat's what I do: ./t5551-http-fetch-smart.sh\n\n> - You probably want to see the version of apache this is running/etc.\n\nThe one that comes with Debian -\nI am not an expert here, what is it that is interesting ?\n\n> - What happens if you kill the apache processes? \n\nI am left with these processes:\n/home/blabla/pu/git -C too-many-refs fetch -q --tags\n/home/blabla/pu/git-remote-http origin http://127.0.0.1:5551/smart/repo.git\n\n> \n> I can't reproduce on my side, but let me see if I can dig a little into\n> it.\n\nThanks, more tips or things I can do are welcome.\nt5551 seems to be flaky - from time to time.\nIt seems that I have it reproducable unstable, so if someone has more\nideas, please.\n\n> \n> Cheers!\n> -Santiago.\n\n\n"},{"id":"326930","messageId":"20170822145112.cr5lz5lgbpo4x66o@LykOS.localdomain","threadId":"46644","inReplyTo":"20170822144357.GA5304@tor.lan","subject":"Re: t5551 hangs ?","fromName":"Santiago Torres","fromEmail":"santiago@nyu.edu","sentAt":"2017-08-22T14:51:13Z","receivedAt":"2017-08-22T14:51:04Z","isPatch":false,"sender":{"key":"santiago@nyu.edu","avatar":"https://avatars.githubusercontent.com/u/3579933?v=4"},"body":"> No concurrency.\n> That's what I do: ./t5551-http-fetch-smart.sh\n\nOh ok! I was just trying to weed out what could out of place. Just to\nmake sure, your old compute is also running debian 8 latest? \n> \n> > - You probably want to see the version of apache this is running/etc.\n> \n> The one that comes with Debian -\n> I am not an expert here, what is it that is interesting ?\n\nI'm not sure, but sometimes it's helpful to look at changelogs between\nversions of packages to get a poiner as to what could be wrong. I wonder\nif it's apache the one that's failing on this case. Probably a paste of\ndpkg-query --show apache would help me try to reproduce..\n\n> \n> > - What happens if you kill the apache processes? \n> \n> I am left with these processes:\n> /home/blabla/pu/git -C too-many-refs fetch -q --tags\n> /home/blabla/pu/git-remote-http origin http://127.0.0.1:5551/smart/repo.git\n> \n\nSo it's probably not an issue with apache, as the socket should be\nhopefully closed gracefully.\n\n> > \n> > I can't reproduce on my side, but let me see if I can dig a little into\n> > it.\n> \n> Thanks, more tips or things I can do are welcome.\n> t5551 seems to be flaky - from time to time.\n> It seems that I have it reproducable unstable, so if someone has more\n> ideas, please.\n\nI'm still unable to reproduce. Do you think you can enable GIT_TRACE,\nGIT_TRACE_PACK and GIT_TRACE_CURL and pastebin/paste what you see?\n\nCheers!\n-Santiago.\n"}]}