From owner-freebsd-ports@FreeBSD.ORG Wed Aug 13 10:40:39 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3D259A; Wed, 13 Aug 2014 10:40:39 +0000 (UTC) Received: from mailrelay010.isp.belgacom.be (mailrelay010.isp.belgacom.be [195.238.6.177]) by mx1.freebsd.org (Postfix) with ESMTP id 493172427; Wed, 13 Aug 2014 10:40:38 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Am8GAJg/61NR8mrQ/2dsb2JhbABagw1STQrNKodIAYESF3eEBAEFViMQCxgJJQ8qHgYTiEYBCMVgEwSOewEBHDMHhEwBBJVDhnWUf4NeOy+BBgkXBA Received: from 208.106-242-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.242.106.208]) by relay.skynet.be with ESMTP; 13 Aug 2014 12:39:28 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.9/8.14.9) with ESMTP id s7DAdQZO001881; Wed, 13 Aug 2014 12:39:26 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Wed, 13 Aug 2014 12:39:26 +0200 From: Tijl Coosemans To: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= Subject: Re: redports and build status Message-ID: <20140813123926.3354a660@kalimero.tijl.coosemans.org> In-Reply-To: References: <20140812205400.47242291@kalimero.tijl.coosemans.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Mailing List , Fernando =?ISO-8859-1?Q?Apestegu=EDa?= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 10:40:39 -0000 On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fr=F6hlich wrote: > On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans wrote: >> On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apestegu=EDa wrote: >>> I built a port in redports and I received a mail notifying that the >>> builds were finished, but it seems redports couldn't figure out if the >>> builds finished successfully. >>> >>> https://redports.org/buildarchive/20140812170901-30860 >>> >>> >> Any ideas of why this happened? >>> >>> Thanks in advance. >> >> I'm seeing a lot of these as well. CCing decke@ >=20 > Yeah, the "finished" state is some rescue state in case something went > terribly wrong. Usually this happens when something inside redports fails > or some backend behaves very weird or if the port creates some very stran= ge > situation like a recursive dependency (which fills up a temporary partiti= on and > then fails). >=20 > If only one of many jobs fails then chances are good that it is some redp= orts > weirdness. If many jobs fail (like in this case) and it is reproducible t= hen the > chances are good that your port is doing something very very bad. I'm seeing these on multiple unrelated ports and with trivial changes. I've now cleared my redports tree, leaving only one unmodified port and it still results in all 'finished'. Maybe redport's internal ports tree got corrupt or one of its cached packages?