Re: t5551 hangs ?
> No concurrency. > That's what I do: ./t5551-http-fetch-smart.sh Oh ok! I was just trying to weed out what could out of place. Just to make sure, your old compute is also running debian 8 latest? > > > - You probably want to see the version of apache this is running/etc. > > The one that comes with Debian - > I am not an expert here, what is it that is interesting ? I'm not sure, but sometimes it's helpful to look at changelogs between versions of packages to get a poiner as to what could be wrong. I wonder if it's apache the one that's failing on this case. Probably a paste of dpkg-query --show apache would help me try to reproduce.. > > > - What happens if you kill the apache processes? > > I am left with these processes: > /home/blabla/pu/git -C too-many-refs fetch -q --tags > /home/blabla/pu/git-remote-http origin http://127.0.0.1:5551/smart/repo.git > So it's probably not an issue with apache, as the socket should be hopefully closed gracefully. > > > > I can't reproduce on my side, but let me see if I can dig a little into > > it. > > Thanks, more tips or things I can do are welcome. > t5551 seems to be flaky - from time to time. > It seems that I have it reproducable unstable, so if someone has more > ideas, please. I'm still unable to reproduce. Do you think you can enable GIT_TRACE, GIT_TRACE_PACK and GIT_TRACE_CURL and pastebin/paste what you see? Cheers! -Santiago. signature.asc Description: PGP signature
Re: t5551 hangs ?
On Tue, Aug 22, 2017 at 01:26:25AM -0400, Santiago Torres wrote: > Hello, Torsten. > > On Tue, Aug 22, 2017 at 07:10:59AM +0200, Torsten Bögershausen wrote: > > Hej, > > I found 2 threads about hanging t5551, one in 2016, and one question > > from Junio somewhen in 2017. > > I have it reproducable here: > > - Debian 8, 64 bit > > - SSD > > - Half-modern processor ;-) > > I don't think the SSD/regular disk have anything to do with it. > > - Are you running tests concurrently? (e.g., with -j x) > - What happens if you run the test individually (i.e., cd t and > ./t5551...) No concurrency. That's what I do: ./t5551-http-fetch-smart.sh > - You probably want to see the version of apache this is running/etc. The one that comes with Debian - I am not an expert here, what is it that is interesting ? > - What happens if you kill the apache processes? I am left with these processes: /home/blabla/pu/git -C too-many-refs fetch -q --tags /home/blabla/pu/git-remote-http origin http://127.0.0.1:5551/smart/repo.git > > I can't reproduce on my side, but let me see if I can dig a little into > it. Thanks, more tips or things I can do are welcome. t5551 seems to be flaky - from time to time. It seems that I have it reproducable unstable, so if someone has more ideas, please. > > Cheers! > -Santiago.
Re: t5551 hangs ?
Hello, Torsten. On Tue, Aug 22, 2017 at 07:10:59AM +0200, Torsten Bögershausen wrote: > Hej, > I found 2 threads about hanging t5551, one in 2016, and one question > from Junio somewhen in 2017. > I have it reproducable here: > - Debian 8, 64 bit > - SSD > - Half-modern processor ;-) I don't think the SSD/regular disk have anything to do with it. - Are you running tests concurrently? (e.g., with -j x) - What happens if you run the test individually (i.e., cd t and ./t5551...) - You probably want to see the version of apache this is running/etc. - What happens if you kill the apache processes? I can't reproduce on my side, but let me see if I can dig a little into it. Cheers! -Santiago. signature.asc Description: PGP signature
Re: t5551 hangs ?
On Thu, May 12, 2016 at 02:40:39AM -0400, Jeff King wrote: > Hmm. Switching to "pu" seems to make things slow on my machine, too, and > the time all goes to fetch. So perhaps there is some recent regression > there. It should be bisectable. It's 66d33af21bd1e398973414435af43d06f2e2099c. I don't think it's hanging, but it is _really_ slow. I'll reply to that patch separately with a report. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: t5551 hangs ?
On Thu, May 12, 2016 at 08:21:10AM +0200, Torsten Bögershausen wrote: > This is the last log that I see: > [...] > ++ git -C too-many-refs fetch -q --tags Not surprising. > And this may be the processes : > (Not sure, probaly need to reboot & clean ?) If you're killing the hung test with "^C", you shouldn't need to; that tries to clean up any processes and shut down apache. > /bin/sh ./t5551-http-fetch-smart.sh -x > 73459 ttys0100:21.45 /Users/tb/projects/git/git.pu/git -C too-many-refs > fetch -q --tags > 73460 ttys0100:00.40 git-remote-http origin > http://127.0.0.1:5551/smart/repo.git > > ps | grep fetch > 73540 ttys0060:00.00 grep fetch > 73025 ttys0100:00.14 /bin/sh ./t5551-http-fetch-smart.sh -x > 73459 ttys0103:40.70 /Users/tb/projects/git/git.pu/git -C too-many-refs > fetch -q --tags I'm surprised not to see fetch-pack in that list. And to see so much CPU going to fetch itself. But perhaps you are simply at a different stage in the test. 3:40 of CPU time is a lot (the whole thing runs in under a minute on my machine). Hmm. Switching to "pu" seems to make things slow on my machine, too, and the time all goes to fetch. So perhaps there is some recent regression there. It should be bisectable. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: t5551 hangs ?
On 12.05.16 05:16, Jeff King wrote: > On Wed, May 11, 2016 at 10:03:45PM +0200, Torsten Bögershausen wrote: > >>> If you are, can you confirm that it's actually hanging, and not just >>> slow? On my system, test 26 takes about a minute to run (which is why we >>> don't do it by default). >> Nearly sure. After 10 minutes, the test was still running. >> >> Yesterday another machine was running even longer. >> >> Any tips, how to debug, are welcome. > > Try running with "-x" to see what the test is doing. It will probably be > in: > >+ git -C too-many-refs fetch -q --tags > > after a while. Check "ps" to see if you have a fetch-pack sub-process > running. It should be writing "have" lines and reading lots of ACK > lines, which you can check via strace. > > If it's blocked on read() or write(), then it's probably some kind of > I/O deadlock. > > -Peff This is the last log that I see: - pack_report: getpagesize()= 4096 pack_report: core.packedGitWindowSize = 1073741824 pack_report: core.packedGitLimit = 8589934592 pack_report: pack_used_ctr= 96001 pack_report: pack_mmap_calls = 48002 pack_report: pack_open_windows= 2 / 2 pack_report: pack_mapped =6605494 /6605494 - +++ perl -e 'print "bla" x 30' +++ command /usr/bin/perl -e 'print "bla" x 30' +++ /usr/bin/perl -e 'print "bla" x 30' ++ tag=blablablablablablablablablablablablablablablablablablablablablablablablablablablablablabla ++ sed -e 's|^:\([^ ]*\) \(.*\)$|\2 refs/tags/blablablablablablablablablablablablablablablablablablablablablablablablablablablablablabla-\1|' ++ git -C too-many-refs fetch -q --tags And this may be the processes : (Not sure, probaly need to reboot & clean ?) /bin/sh ./t5551-http-fetch-smart.sh -x 73459 ttys0100:21.45 /Users/tb/projects/git/git.pu/git -C too-many-refs fetch -q --tags 73460 ttys0100:00.40 git-remote-http origin http://127.0.0.1:5551/smart/repo.git ps | grep fetch 73540 ttys0060:00.00 grep fetch 73025 ttys0100:00.14 /bin/sh ./t5551-http-fetch-smart.sh -x 73459 ttys0103:40.70 /Users/tb/projects/git/git.pu/git -C too-many-refs fetch -q --tags Beside that, reverting the last 2 commits on 5551 doesn't seem to help: Revert "t5551: make the test for extra HTTP headers more robust" Revert "submodule: ensure that -c http.extraheader is heeded" -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: t5551 hangs ?
On Wed, May 11, 2016 at 10:03:45PM +0200, Torsten Bögershausen wrote: > > If you are, can you confirm that it's actually hanging, and not just > > slow? On my system, test 26 takes about a minute to run (which is why we > > don't do it by default). > Nearly sure. After 10 minutes, the test was still running. > > Yesterday another machine was running even longer. > > Any tips, how to debug, are welcome. Try running with "-x" to see what the test is doing. It will probably be in: + git -C too-many-refs fetch -q --tags after a while. Check "ps" to see if you have a fetch-pack sub-process running. It should be writing "have" lines and reading lots of ACK lines, which you can check via strace. If it's blocked on read() or write(), then it's probably some kind of I/O deadlock. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: t5551 hangs ?
On 11.05.16 19:31, Jeff King wrote: > On Wed, May 11, 2016 at 07:13:56PM +0200, Torsten Bögershausen wrote: > >> On 10.05.16 09:08, Johannes Schindelin wrote: >> - I'm not sure, if this is the right thread to report on - >> >> It seems as if t5551 is hanging ? >> This is the last line from the log: >> ok 25 - large fetch-pack requests can be split across POSTs > > Are you running the tests with "--long" or GIT_TEST_LONG in the > environment? The next line should show it skipping test 26 unless one of > those is set. Yes > > If you are, can you confirm that it's actually hanging, and not just > slow? On my system, test 26 takes about a minute to run (which is why we > don't do it by default). Nearly sure. After 10 minutes, the test was still running. Yesterday another machine was running even longer. Any tips, how to debug, are welcome. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: t5551 hangs ?
On Wed, May 11, 2016 at 07:13:56PM +0200, Torsten Bögershausen wrote: > On 10.05.16 09:08, Johannes Schindelin wrote: > - I'm not sure, if this is the right thread to report on - > > It seems as if t5551 is hanging ? > This is the last line from the log: > ok 25 - large fetch-pack requests can be split across POSTs Are you running the tests with "--long" or GIT_TEST_LONG in the environment? The next line should show it skipping test 26 unless one of those is set. If you are, can you confirm that it's actually hanging, and not just slow? On my system, test 26 takes about a minute to run (which is why we don't do it by default). > I have 7 such processes running: > /trash directory.t5551-http-fetch-smart/httpd -f > /Users/tb/projects/git/git.pu/t/lib-httpd/apache.conf -DDarwin -c Listen > 127.0.0.1:5551 -k start That's normal while the test is running; apache pre-forks a bunch of worker threads. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
