Date: Wed, 13 Aug 2014 18:54:57 +0200 From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> To: ajtiM <lumiwa@gmail.com> Cc: Tijl Coosemans <tijl@freebsd.org>, =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= <decke@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: redports and build status Message-ID: <CAGwOe2Ys14pC3L_3zNGyy54JFheXofRkECYZjMxTGSFL3%2Bs=7A@mail.gmail.com> In-Reply-To: <CAGwOe2b-2nAyjQgqSv88YJAvg=mp2Q6ErDQ3zeMVUcWR=jwREg@mail.gmail.com> References: <CAGwOe2bfPNknz=X_dHAmnJgVTM3F9huueZXwWr48yYOFY6BR9g@mail.gmail.com> <20140813123926.3354a660@kalimero.tijl.coosemans.org> <CAGwOe2bABx-7zcfgR3Wj_6=ZFfHvFtf-oYggNs1NR5MjS1=SRg@mail.gmail.com> <17051586.gQbKyLmFOD@lumiwa.farms.net> <CAGwOe2b-2nAyjQgqSv88YJAvg=mp2Q6ErDQ3zeMVUcWR=jwREg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 13, 2014 at 6:16 PM, Fernando Apestegu=C3=ADa <fernando.apesteguia@gmail.com> wrote: > On Wed, Aug 13, 2014 at 5:50 PM, Ajtim <lumiwa@gmail.com> wrote: >> On Wednesday 13 August 2014 17:11:28 Fernando Apestegu=C3=ADa wrote: >>> On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans <tijl@freebsd.org> wro= te: >>> > On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fr=C3=B6hlich wrote: >>> >> On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans <tijl@freebsd.org> w= rote: >>> >>> On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apestegu=C3=ADa wrote: >>> >>>> I built a port in redports and I received a mail notifying that th= e >>> >>>> 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@ >>> >> >>> >> Yeah, the "finished" state is some rescue state in case something we= nt >>> >> terribly wrong. Usually this happens when something inside redports = fails >>> >> or some backend behaves very weird or if the port creates some very >>> >> strange >>> >> situation like a recursive dependency (which fills up a temporary >>> >> partition and then fails). >>> >> >>> >> If only one of many jobs fails then chances are good that it is some >>> >> redports weirdness. If many jobs fail (like in this case) and it is >>> >> reproducible then the chances are good that your port is doing somet= hing >>> >> 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 a= nd >>> > it still results in all 'finished'. Maybe redport's internal ports t= ree >>> > got corrupt or one of its cached packages? >>> >>> Mine is modified but nothing to do with dependencies or such. However >>> this problem is reproducible. This is the port: >>> >>> https://redports.org/browser/fernape/lang/basic256?rev=3D30358 >>> >>> I don't see very bad things there or at least not compared with the >>> previous revision which finished with "success" >>> >>> 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. >>> Just tried another port and it finished without being able to figure out the outcome of the building process. The differences between the revision that "worked" and the one that didn't, are trivial: https://redports.org/changeset/30460/fernape Cheers. >>> Regards >> >> http://forums.freebsd.org/viewtopic.php?f=3D22&t=3D44800&start=3D75 > > Sorry, but I don't see how that thread is related to this one... > >> >> -- >> ajtiM >> -------- >> http://www.redbubble.com/people/lumiwa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGwOe2Ys14pC3L_3zNGyy54JFheXofRkECYZjMxTGSFL3%2Bs=7A>