From owner-freebsd-ports@FreeBSD.ORG Sun Feb 16 19:19:47 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 6621FFEC for ; Sun, 16 Feb 2014 19:19:47 +0000 (UTC) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1FFAD16C7 for ; Sun, 16 Feb 2014 19:19:47 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id wp18so15973749obc.22 for ; Sun, 16 Feb 2014 11:19:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BTstxYYa7giqqFrjo7SEGritMJtz6Xlsc7nmUZ7TiR4=; b=EzJQ7PKVCZRDHzKZdwsUjK7+1MokxkMP1a9s0RpwO/T2hVGovSMdl2DIB8TNx3cOlc eRfVs+hIjHTj+8whIhlAps7aLTxelkubiU5ZbwnzLnDu4DmnO8sPXhxPosHFKk9HKnmR JMj8TGGatjFUH7BgfHbOlo6ppyeXIc8FF6Ei4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=BTstxYYa7giqqFrjo7SEGritMJtz6Xlsc7nmUZ7TiR4=; b=bdoDlXBGdVbLFhyiIwet/Z7cxXfd5MxKfhLrzYBPzyh8pHFzZ2LBBcVFlihGvJs2vK rYSrSV5NV3A/GEKpnh8Tee0xAEc0MDoJBgEaC3nvkf7MA71Wlq7Dl8KCzzWlKmBQqCdw f15Ud5aQkH0hXSFHPI/NhSaRRBqyDNObQ9qxZO1l+2svlNSjhftNJU2PjwtQWWnk0lDo qJgvxv5VA94yeBCh+mut91sorH0W6zxgNuaa4zVTtO7bo87KuMxWhhyol+gUyKTmdSvQ 1FFeV8qzbENdpjjPPLfPNvJwTQbOVitupxu7opIrGyXc/Agh948Xr4gRmkRxXWijTIqS JGsw== X-Gm-Message-State: ALoCoQmJFE/6wlLCC1UTMwG4J2hVJ41vuk/3b4TmWpdY5i43pdLwC0nUiFc0MTtVX0x+jfbkF+E1 MIME-Version: 1.0 X-Received: by 10.182.233.201 with SMTP id ty9mr17522891obc.29.1392578386236; Sun, 16 Feb 2014 11:19:46 -0800 (PST) Received: by 10.76.144.71 with HTTP; Sun, 16 Feb 2014 11:19:46 -0800 (PST) X-Originating-IP: [89.144.223.201] Received: by 10.76.144.71 with HTTP; Sun, 16 Feb 2014 11:19:46 -0800 (PST) In-Reply-To: <52FFC900.2010807@saltant.com> References: <52F8E7BB.4060700@saltant.com> <52FFA9A1.3050601@saltant.com> <52FFC900.2010807@saltant.com> Date: Sun, 16 Feb 2014 20:19:46 +0100 Message-ID: Subject: Re: Redport builds are all "finished" without logs From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: "John W. O'Brien" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: xmj@chaot.net, ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Feb 2014 19:19:47 -0000 Am 15.02.2014 21:07 schrieb "John W. O'Brien" : > > On 2/15/14 12:53 PM, John W. O'Brien wrote: > > On 2/10/14 9:52 AM, John W. O'Brien wrote: > >> Could you help me understand what's going on with this build [0]? Did an > >> admin kill the job, and if so, why? Otherwise, what happened and is it > >> because I'm doing something wrong? > >> > >> [0] https://redports.org/buildarchive/20140210032800-24135/ > > > > Continuing to troubleshoot this. I've been adding ports to TEST_DEPENDS > > one by one, and found an instance where the /before/ [1] works but the > > /after/ [2] does not. > > > > The implicated port is math/py-statsmodels (maintainer CC'd). > > > > I'm still not clear on the circumstances under which Redports winds up > > in the "finished" state, and consequently am unable to avoid it or work > > around it. Any help or advice would be appreciated. > > > > [1] https://redports.org/buildarchive/20140215154500-1493/ > > [2] https://redports.org/buildarchive/20140215163200-621/ > > I see the problem. math/py-statsmodels depends on math/py-pandas. So the > bad news is that I cannot include the former in TEST_DEPENDS for the > latter and expect much at all from Redports. The good news is that I can > now fix my port to be more readily testable. > > For the benefit of those who come after, would it make sense to augment > the description of the "finished" state [3] to mention the possibility > of circular dependencies, which don't appear to be covered by the other > detectable termination conditions? > > Regards, > John > > [3] https://redports.org/wiki/Buildstatus The finished state is not something the user should see at all. The truth is that there are cases that redports is unable to detect because of bugs inside tinderbox or in the redports scripts or because of extreme cases like circular dependencies like in your cases. In the beginning circular dependencies took the whole backend down but I worked around it by setting the maximum size of the tinderbox environment directory to a very small value so it fails after some minutes of excessive i/o and cpu usage. So except from "when the tinderbox job fails in a strange way and the environment directory is 100=F7 full" I see no chance how to detect that ca= se and I don't want to build a feature based on a dirty workaround. The right way to fix that is to add a circular dependency check to tinderbox and then I can read out that error properly.