git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: t5561 failing after make PROFILE=GEN
Date: Wed, 23 Sep 2015 21:41:35 -0400	[thread overview]
Message-ID: <20150924014135.GA6442@sigill.intra.peff.net> (raw)
In-Reply-To: <56034232.6030100@gmx.net>

On Thu, Sep 24, 2015 at 02:22:10AM +0200, Stephan Beyer wrote:

> I only checked for profile builds and first tried to bisect the issue,
> which went terribly wrong because using older Git commits (unluckily I
> can't say now how far you should go back in history), the test failed or
> succeeded randomly. So it always found different (and always unrelated)
> commits using "git bisect run".
> However, in the latest versions, it *always* fails for a profile build
> (and *never* for a non-profile build, at least here).
> 
> Maybe this needs some more investigation?

I don't think so. The tests have always been pretty solid, but I think
the profile-build code was broken for a long while.

> Hmm, but why is the profile build of http-backend "slower"? (Or am I
> getting it wrong?)

Remember that there are two phases to the profile build: first we build
with profile-recording on, run the tests, and then build the optimized
version with the output written during the test-run. And it's this first
build that is failing the tests. I don't know exactly how the
profile-recording is implemented, but I imagine that it records counters
as it runs, and then after we call exit() it dumps the counters to a
file.

So the profile-generation version probably _is_ slower overall, but it
is really the pause between exit() and the process actually ending that
is the problem here (because the client thinks we are done and proceeds,
but apache is waiting for the CGI to exit).

> > Touching the apache logfile ourselves is inherently racy.
> 
> It would not be racy if we started/stopped apache before/after each test
> (and only append to the logfile after each apache shutdown). But that
> would slow it down a lot.

True, though that would be really slow (it may also still be racy; I
don't know if Apache would flush out the log if it gets a shutdown
signal or not).

> That's a very good idea. (I just sent a patch with a possible realization.)

Thanks, I'll give it a look.

-Peff

      reply	other threads:[~2015-09-24  1:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 23:21 t5561 failing after make PROFILE=GEN Stephan Beyer
2015-09-23 23:24 ` Jeff King
2015-09-24  0:20   ` [PATCH] t5561: get rid of racy appending to logfile Stephan Beyer
2015-09-24  1:45     ` Jeff King
2015-09-24 18:12       ` Stephan Beyer
2015-09-24 18:23         ` Jeff King
2015-09-25 15:50         ` Junio C Hamano
2015-09-24  0:22   ` t5561 failing after make PROFILE=GEN Stephan Beyer
2015-09-24  1:41     ` Jeff King [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150924014135.GA6442@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=s-beyer@gmx.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).