Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Feb 2022 12:49:56 +0100 (CET)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        Philip Paeps <philip@freebsd.org>
Cc:        clusteradm@freebsd.org, Ports Management Team <portmgr@freebsd.org>, freebsd-arm@freebsd.org
Subject:   Re: aarch64 build cluster and linux64.ko
Message-ID:  <1414783579.189.1643975396033@localhost>
In-Reply-To: <F7DEF3FC-AD19-4F84-9C3C-30EC84D643B3@freebsd.org>
References:  <1041004715.975.1643961552511@localhost> <F7DEF3FC-AD19-4F84-9C3C-30EC84D643B3@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_188_1079252898.1643975395742
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

 
Van: Philip Paeps <philip@freebsd.org>
Datum: vrijdag, 4 februari 2022 12:05
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: Ports Management Team <portmgr@freebsd.org>, freebsd-arm@freebsd.org, clusteradm@freebsd.org
Onderwerp: Re: aarch64 build cluster and linux64.ko
> 
> On 2022-02-04 15:59:12 (+0800), Ronald Klop wrote:
> > Philip Paeps wrote:
> >> On 2022-01-26 08:58:20 (+0800), Philip Paeps wrote:
> >> I've upgraded one of the package builders (ampere1.nyi.freebsd.org) >> with a build including linux64.ko.  The module seems to load.  
> >> portmgr might need to do something to the builds to actually use it >> though.
> >>
> >> I'll upgrade the other aarch64 package builder when it finishes its >> current build.
> >
> > Thank you. 122arm64 quarterly build fine. 130arm64 quarterly is > hanging in :sanity: for 48 hours already. I think it is stuck. Would > you have time to check?
> 
> If I understand the automation/scheduling correctly, ampere1 started a new 130arm64 quarterly build while I was upgrading it.  That build got stuck in :sanity:.  After being upgraded, it started on the next build in the queue, which is still running now.  I believe it should start on a 130arm64 build after this.
> 
> Philip
> 
> -- 
> Philip Paeps
> Senior Reality Engineer
> Alternative Enterprises
> 
> 
> 


Hi,

Thanks for your reply.
I was looking at https://pkg-status.freebsd.org/builds?type=package&all=1 which might have some stale data. Although it also mentions a succesful 122arm64 build with "Host OSVERSION: 1400050" in the build log of a pkg.
This site: http://ampere1.nyi.freebsd.org/ shows what you are telling. Sorry for the noise and thanks for all this maintenance. If can help I would be happy to.

Regards,
Ronald.
 
------=_Part_188_1079252898.1643975395742
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html><head></head><body>&nbsp;
<p><strong>Van:</strong> Philip Paeps &lt;philip@freebsd.org&gt;<br />
<strong>Datum:</strong> vrijdag, 4 februari 2022 12:05<br />
<strong>Aan:</strong> Ronald Klop &lt;ronald-lists@klop.ws&gt;<br />
<strong>CC:</strong> Ports Management Team &lt;portmgr@freebsd.org&gt;, freebsd-arm@freebsd.org, clusteradm@freebsd.org<br />
<strong>Onderwerp:</strong> Re: aarch64 build cluster and linux64.ko</p>

<blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">
<div class="MessageRFC822Viewer" id="P">
<div class="TextPlainViewer" id="P.P">On 2022-02-04 15:59:12 (+0800), Ronald Klop wrote:<br />
&gt; Philip Paeps wrote:<br />
&gt;&gt; On 2022-01-26 08:58:20 (+0800), Philip Paeps wrote:<br />
&gt;&gt; I've upgraded one of the package builders (ampere1.nyi.freebsd.org) &gt;&gt; with a build including linux64.ko. &nbsp;The module seems to load. &nbsp;<br />
&gt;&gt; portmgr might need to do something to the builds to actually use it &gt;&gt; though.<br />
&gt;&gt;<br />
&gt;&gt; I'll upgrade the other aarch64 package builder when it finishes its &gt;&gt; current build.<br />
&gt;<br />
&gt; Thank you. 122arm64 quarterly build fine. 130arm64 quarterly is &gt; hanging in :sanity: for 48 hours already. I think it is stuck. Would &gt; you have time to check?<br />
<br />
If I understand the automation/scheduling correctly, ampere1 started a new 130arm64 quarterly build while I was upgrading it. &nbsp;That build got stuck in :sanity:. &nbsp;After being upgraded, it started on the next build in the queue, which is still running now. &nbsp;I believe it should start on a 130arm64 build after this.<br />
<br />
Philip<br />
<br />
--&nbsp;<br />
Philip Paeps<br />
Senior Reality Engineer<br />
Alternative Enterprises</div>

<hr /></div>
</blockquote>
<br />
<br />
Hi,<br />
<br />
Thanks for your reply.<br />
I was looking at https://pkg-status.freebsd.org/builds?type=package&amp;all=1 which might have some stale data. Although it also mentions a succesful 122arm64 build with &quot;Host OSVERSION: 1400050&quot; in the build log of a pkg.<br />
This site: http://ampere1.nyi.freebsd.org/ shows what you are telling. Sorry for the noise and thanks for all this maintenance. If can help I would be happy to.<br />
<br />
Regards,<br />
Ronald.<br />
&nbsp;</body></html>
------=_Part_188_1079252898.1643975395742--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1414783579.189.1643975396033>