t5551 hangs ?
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 ;-)
The last thing I can see is:
ok 29 - test allowanysha1inwant with unreachable
-----------
A simplified ps -ef shows:/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 /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 /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 /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 /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 /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 /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 /home/blalbla/git -C too-many-refs fetch -q --tags/home/blalbla/git-remote-http origin http://127.0.0.1:5551/smart/repo.git
-------------
The tests passes on another box (real old laptop, spinning disk)
Anything that can be done to debug it ?
Hello, Torsten.
Quoted 7 lines · Torsten Bögershausen
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.
Quoted 11 lines · Santiago Torres
Hello, Torsten.
Quoted 7 lines · Torsten Bögershausen
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 ;-)
Quoted 5 lines
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
Quoted 1 line
- 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 ?
Quoted 1 line
- 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
Quoted 3 lines
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.
Quoted 3 lines
Cheers!
-Santiago.
Quoted 2 lines
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?
Quoted 5 lines
Quoted 2 lines
- 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..
Quoted 7 lines
Quoted 2 lines
- 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-httporigin 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.
Quoted 8 lines
Quoted 3 lines
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.