zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <schizo@debian.org>
To: "Christian T. Steigies" <cts@debian.org>
Cc: zsh-workers@sunsite.dk, sbuild@packages.debian.org,
	troup@debian.org, Q@ping.be
Subject: Re: zsh (4.2.0-10)
Date: Thu, 13 May 2004 10:12:37 -0400	[thread overview]
Message-ID: <20040513141237.GA525@scowler.net> (raw)
In-Reply-To: <20040513140213.GA26274@auric.debian.org>

> According the manpage, I sent a kill -s SIGCONT. Did that, this is what
> happened:

Technically it should be "kill -s CONT".

> ../../Test/B04read.ztst: starting.
> make[2]: *** [check] Terminated
> make[1]: *** [check] Terminated
> Build killed with signal 15 after 150 minutes of inactivity
> Build killed with signal 9 after 5 minutes of inactivity
> ******************************************************************************

Probably sbuild sent the SIGTERM long before you sent the SIGCONT, and
the build didn't react until you did.

Previously, this had only been seen using sbuild on ultrasparc, and
recently Kurt Roeckx reported a problem using sbuild on amd64.  I assume
you're using sbuild on m68k.  Yes?


       reply	other threads:[~2004-05-13 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040513074011.GA31678@skeeve>
     [not found] ` <20040513132408.GA32597@scowler.net>
     [not found]   ` <20040513133541.GA24070@auric.debian.org>
     [not found]     ` <20040513140213.GA26274@auric.debian.org>
2004-05-13 14:12       ` Clint Adams [this message]
     [not found]         ` <20040513144300.GA26771@auric.debian.org>
2004-05-13 16:06           ` Clint Adams
2004-05-13 21:30             ` Clint Adams
     [not found]             ` <20040513192544.GA11594@skeeve>
2004-05-14  2:56               ` Goswin von Brederlow
2004-05-14  4:29                 ` Clint Adams

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=20040513141237.GA525@scowler.net \
    --to=schizo@debian.org \
    --cc=Q@ping.be \
    --cc=cts@debian.org \
    --cc=sbuild@packages.debian.org \
    --cc=troup@debian.org \
    --cc=zsh-workers@sunsite.dk \
    /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://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).