From nobody Fri Feb 04 11:49:56 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id ADEC519BEB8C for ; Fri, 4 Feb 2022 11:49:58 +0000 (UTC) (envelope-from SRS0=vdMV=ST=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jqv3T483Fz4VSJ; Fri, 4 Feb 2022 11:49:57 +0000 (UTC) (envelope-from SRS0=vdMV=ST=klop.ws=ronald-lists@realworks.nl) Date: Fri, 4 Feb 2022 12:49:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1643975395; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Tr59TTsMV0bY6DyXrqGV9si7t/CBKkuY9VygdWf5i1g=; b=zznSqZ8/5hyT1DuEXdsp0ukSuhABmY2CfxOWoMpmOnEIm3YL9sVXymlpf0/cjGoSTUE7xQ jgkzhcnZg3lWHFtOgwjqI6xe2ZvCcOUBOFZsCEd2m3M7fLxwDsOBEiGTpuuQLpDnO5P5zq tftqi5fKsBqBWqHWa7HVQzQxEQSGIEiXYFVKfo9+TSiHq+6iN+jDb/h53hyvpqH4SLWLgF TK67CtscTDhq89tY2H2vG3K9EThJf8NxkzOfQPdQzmW1pi41Xjg8eYRcYeFcKqGhlXrbII VEvLGvUhh5lzgvphJecWI/8KeJqaPHaVfQLLcqOLqiZW09iAh2R+SiR4QYZIEQ== From: Ronald Klop To: Philip Paeps Cc: clusteradm@freebsd.org, Ports Management Team , freebsd-arm@freebsd.org Message-ID: <1414783579.189.1643975396033@localhost> In-Reply-To: References: <1041004715.975.1643961552511@localhost> Subject: Re: aarch64 build cluster and linux64.ko List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_188_1079252898.1643975395742" X-Mailer: Realworks (594.12.ee219b8) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4Jqv3T483Fz4VSJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b="zznSqZ8/"; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=vdMV=ST=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=vdMV=ST=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-arm]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=vdMV=ST=klop.ws=ronald-lists@realworks.nl]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=vdMV=ST=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_188_1079252898.1643975395742 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Philip Paeps Datum: vrijdag, 4 februari 2022 12:05 Aan: Ronald Klop CC: Ports Management Team , 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  

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