On 2018-2-20 14:43 , Ryan Schmidt wrote:
>
> On Feb 19, 2018, at 18:14, Joshua Root wrote:
>
>> On 2018-2-20 10:14 , Ryan Schmidt wrote:
>>>
>>> As far as I know there is no reason why we could not fix the random build
>>> order problem while staying on buildbot 0.8. We would just need to write
Hi,
On Mon, Feb 19, 2018 at 11:32:50PM +0100, Mojca Miklavec wrote:
> From 10th to 14th March we'll be meeting at the 2nd MacPorts Meeting
> in Slovenia.
>
> https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018
>
> During the last meeting we borrowed two older Mac Pros (box format,
>
On Feb 19, 2018, at 16:49, Mojca Miklavec wrote:
> Are there any thoughts about migration to buildbot 1.0 (from Ryan in
> particular)?
>
> I wanted to seize the opportunity of some hacking during the MacPorts
> meeting next month to potentially migrate to buildbot version one, but
> there is
On 2018-2-20 10:14 , Ryan Schmidt wrote:
>
> As far as I know there is no reason why we could not fix the random build
> order problem while staying on buildbot 0.8. We would just need to write the
> code to add an "order" integer to each spawned portbuilder, then write a
> function to return
On Feb 19, 2018, at 18:14, Joshua Root wrote:
> On 2018-2-20 10:14 , Ryan Schmidt wrote:
>>
>> As far as I know there is no reason why we could not fix the random build
>> order problem while staying on buildbot 0.8. We would just need to write the
>> code to add an "order" integer to each
Hi,
>From 10th to 14th March we'll be meeting at the 2nd MacPorts Meeting
in Slovenia.
https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018
During the last meeting we borrowed two older Mac Pros (box format,
pretty old, but with quite some cores and speed) which we used for
heavily
Hi,
Are there any thoughts about migration to buildbot 1.0 (from Ryan in
particular)?
I wanted to seize the opportunity of some hacking during the MacPorts
meeting next month to potentially migrate to buildbot version one, but
there is one quite severe drawback, and that's the display of
