> 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
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 reproducabl
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 thi
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 sho
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 t
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",
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
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 sti
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
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
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
I have 7 such processes running:
/trash directory.t5551-http-f
11 matches
Mail list logo