Re: gcc 7, 6 builds killed on kfreebsd

Steven Chamberlain wrote: > Christoph Egger wrote: > > | WARNING: 30 signals -- adjust and recompile. > > That comes from pkill, which recently stopped working. This means, the > build already hung / timed out and sbuild is merely failing to kill it. The warning messages from libprocps are

Re: gcc 7, 6 builds killed on kfreebsd

Unsubscribe > On Jan 9, 2017, at 9:04 AM, Steven Chamberlain wrote: > > Christoph Egger wrote: >> | WARNING: 30 signals -- adjust and recompile. > > That comes from pkill, which recently stopped working. This means, the > build already hung / timed out and sbuild is merely

Re: gcc 7, 6 builds killed on kfreebsd

Christoph Egger wrote: > | WARNING: 30 signals -- adjust and recompile. That comes from pkill, which recently stopped working. This means, the build already hung / timed out and sbuild is merely failing to kill it. For that I've just filed Bug#850717 against procps: [kfreebsd] pkill fails,

Re: gcc 7, 6 builds killed on kfreebsd

Hi! Christoph Egger wrote: > I've just killed the gcc builds on kfreebsd. THey're all looping with a > > | WARNING: 30 signals -- adjust and recompile. Thanks; it seems to have happened again though on kfreebsd-amd64 (stuck building gcc-6 and gcc-snapshot for 5+ days). I will look into this

gcc 7, 6 builds killed on kfreebsd

Hi! I've just killed the gcc builds on kfreebsd. THey're all looping with a | WARNING: 30 signals -- adjust and recompile. Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer signature.asc Description: PGP signature