From owner-freebsd-ports@FreeBSD.ORG Wed Aug 13 15:50:41 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 9CF1C720; Wed, 13 Aug 2014 15:50:41 +0000 (UTC) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 537AB2867; Wed, 13 Aug 2014 15:50:41 +0000 (UTC) Received: by mail-ig0-f180.google.com with SMTP id l13so2142386iga.7 for ; Wed, 13 Aug 2014 08:50:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:reply-to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=lFS8cvfm9YREzCl3bsQ1l5si1qKi+DAUSzafU8LqrJE=; b=acbX0QqOGOQIEdK35IzgitE1+F9zlnaTlcOFhIOoN+RKt9w5sTzPeDooCKQVxFQTPr utr+0qSeBfqGC7DiHVM1CvW5XS+B7yBjQ1FM7C2WpXdATo8nBHxbzosk13YJ93Hfv1RL 5RqWEpZ0TgzEpY9j/nbunkV/eOdaMzSbBHyzpxl92b+7TkBMTFXwdYc+g3eSPMh68Uc9 AqM03oVjujmik9ImCaUubQfslZZgZamcTx/q1HtE5SHEu1cbxNIp6jp+UmQiTjOkBZp1 Q94MoecKDo/ZlBApwycaM95/OjEwrWMw/YLm0RSqHcHGnC/Q6AmN8XlXwTtXc56C8/nM io7g== X-Received: by 10.50.143.73 with SMTP id sc9mr49542969igb.29.1407945040778; Wed, 13 Aug 2014 08:50:40 -0700 (PDT) Received: from lumiwa.farms.net (pool-70-105-226-207.port.east.myfairpoint.net. [70.105.226.207]) by mx.google.com with ESMTPSA id n1sm74286972igp.1.2014.08.13.08.50.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 08:50:39 -0700 (PDT) From: Ajtim To: freebsd-ports@freebsd.org Reply-To: lumiwa@gmail.com Subject: Re: redports and build status Date: Wed, 13 Aug 2014 11:50:36 -0400 Message-ID: <17051586.gQbKyLmFOD@lumiwa.farms.net> User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE-p7; KDE/4.12.5; amd64; ; ) In-Reply-To: References: <20140813123926.3354a660@kalimero.tijl.coosemans.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Cc: Tijl Coosemans , Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= , 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 15:50:41 -0000 On Wednesday 13 August 2014 17:11:28 Fernando Apestegu=EDa wrote: > On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans w= rote: > > 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. > >>>>=20 > >>>> https://redports.org/buildarchive/20140812170901-30860 > >>>=20 > >>> Any ideas of why this happened? > >>>=20 > >>>> Thanks in advance. > >>>=20 > >>> 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 redport= s fails > >> or some backend behaves very weird or if the port creates some ver= y > >> strange > >> situation like a recursive dependency (which fills up a temporary > >> partition and then fails). > >>=20 > >> If only one of many jobs fails then chances are good that it is so= me > >> redports weirdness. If many jobs fail (like in this case) and it i= s > >> reproducible then the chances are good that your port is doing som= ething > >> very very bad. > >=20 > > I'm seeing these on multiple unrelated ports and with trivial chang= es. > > 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? >=20 > Mine is modified but nothing to do with dependencies or such. However= > this problem is reproducible. This is the port: >=20 > https://redports.org/browser/fernape/lang/basic256?rev=3D30358 >=20 > I don't see very bad things there or at least not compared with the > previous revision which finished with "success" >=20 > Can you think of anything I can try? I'm willing to help. I got used > to run successfully tests in redports to attach them to my PR's and I= > don't want to update this port until it builds properly. >=20 > Regards http://forums.freebsd.org/viewtopic.php?f=3D22&t=3D44800&start=3D75 --=20 ajtiM -------- http://www.redbubble.com/people/lumiwa