Date: Wed, 13 Aug 2014 12:39:26 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= <decke@FreeBSD.org> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org>, Fernando =?ISO-8859-1?Q?Apestegu=EDa?= <fernando.apesteguia@gmail.com> Subject: Re: redports and build status Message-ID: <20140813123926.3354a660@kalimero.tijl.coosemans.org> In-Reply-To: <CAE-m3X2wQ0e3oVDn=ACkCXrAn5ZK%2BZhyUsD5RnKvfNbBRtfSxA@mail.gmail.com> References: <CAGwOe2bfPNknz=X_dHAmnJgVTM3F9huueZXwWr48yYOFY6BR9g@mail.gmail.com> <20140812205400.47242291@kalimero.tijl.coosemans.org> <CAE-m3X2wQ0e3oVDn=ACkCXrAn5ZK%2BZhyUsD5RnKvfNbBRtfSxA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fr=F6hlich wrote: > On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans <tijl@freebsd.org> 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140813123926.3354a660>