redports and build status

Fernando Apesteguía fernando.apesteguia at gmail.com
Wed Aug 13 15:11:32 UTC 2014


On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans <tijl at freebsd.org> wrote:
> On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fröhlich wrote:
>> On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans <tijl at freebsd.org> wrote:
>>> On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía 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@
>>
>> 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 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 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?

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=30358

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.

Regards


More information about the freebsd-ports mailing list