From: Santiago Torres <santiago@nyu.edu>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: t5551 hangs ?
Date: Tue, 22 Aug 2017 01:26:25 -0400 [thread overview]
Message-ID: <20170822052625.wzlhckjm6gwr2q6f@LykOS.localdomain> (raw)
In-Reply-To: <20170822051059.GA26331@tor.lan>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-22 5:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 5:10 t5551 hangs ? Torsten Bögershausen
2017-08-22 5:26 ` Santiago Torres [this message]
2017-08-22 14:43 ` Torsten Bögershausen
2017-08-22 14:51 ` Santiago Torres
-- strict thread matches above, loose matches on Subject: below --
2016-05-09 6:18 [PATCH v7 0/3] Add support for sending additional HTTP headers (part 2) Johannes Schindelin
2016-05-10 7:08 ` [PATCH v8 " Johannes Schindelin
2016-05-10 7:08 ` [PATCH v8 2/3] t5551: make the test for extra HTTP headers more robust Johannes Schindelin
2016-05-11 17:13 ` t5551 hangs ? Torsten Bögershausen
2016-05-11 17:31 ` Jeff King
2016-05-11 20:03 ` Torsten Bögershausen
2016-05-12 3:16 ` Jeff King
2016-05-12 6:21 ` Torsten Bögershausen
2016-05-12 6:40 ` Jeff King
2016-05-12 7:29 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170822052625.wzlhckjm6gwr2q6f@LykOS.localdomain \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.