[Buildbot-commits] [Buildbot] #2454: SiGHUP doesn't always work

Buildbot trac trac at buildbot.net
Tue May 7 01:47:45 UTC 2013

#2454: SiGHUP doesn't always work
Reporter:  virgilg          |       Owner:
    Type:  support-request  |      Status:  new
Priority:  major            |   Milestone:  ongoing
 Version:  0.8.7p1          |  Resolution:
Keywords:                   |
Changes (by dustin):

 * type:  defect => support-request
 * milestone:  undecided => ongoing


 I don't mean that you're seeing things different from the *expected*
 behavior of the code - I mean that you're seeing things that indicate
 you're running different code than I'm looking at, which makes this
 impossible to diagnose.  Your system behaves *radically* differently from
 any other user's, and we need to find the reason for that.  You've been
 feeding me interesting tidbits, but ultimately it's up to you to find out
 what makes your system different from everyone else's, and either fix that
 or describe the difference so that we can adjust Buildbot to accomodate.

 You do have two copies - three, in fact - of the code installed.  You've
 pasted a copy of them in the previous comment.  I'd suggest deliberately
 introducing a syntax error in the "wrong" eventual.py as a way of checking
 that it's not being run.

 The SIGHUP handler calls eventually, which prints a message to twistd.log.
 So either the signal isn't being delivered, or the handler isn't logging,
 or you're looking in twistd.log.

 This bug isn't particularly actionable for us as Buildbot developers until
 you can narrow down exactly what's going on.  This may be a bug in
 Buildbot, but it may not.  That's going to take some serious detective
 work from you.

Ticket URL: <http://trac.buildbot.net/ticket/2454#comment:11>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation

More information about the Commits mailing list