Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Jan 2025 10:41:20 +0100 (CET)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        freebsd-arm@freebsd.org, freebsd-pkg@FreeBSD.org
Cc:        FreeBSD Mailing List <freebsd-ports@freebsd.org>
Subject:   trimming_ignore poudriere failure
Message-ID:  <1710947431.3032.1737106880170@localhost>
In-Reply-To: <4226686C-BADB-4D9D-9CF9-54C3AF1692EB@yahoo.com>
References:  <4226686C-BADB-4D9D-9CF9-54C3AF1692EB.ref@yahoo.com> <4226686C-BADB-4D9D-9CF9-54C3AF1692EB@yahoo.com>

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

Hi,

I'm trying to get some more attention to the 'trimming_ignore' error in the pkg building cluster.

See latest 141releng-armv7-quarterly failure: https://pkg-status.freebsd.org/ampere1/.

The part of the logs about this error are not public (AFAIK). So could somebody with access take a look what is happening?

Regards,
Ronald.

 
Van: Mark Millard <marklmi@yahoo.com>
Datum: zaterdag, 11 januari 2025 04:21
Aan: Ronald Klop <ronald-lists@klop.ws>, FreeBSD Mailing List <freebsd-ports@freebsd.org>
Onderwerp: RE: pkg build FreeBSD:13:armv7_latest failing with trimming_ignore
> 
> Ronald Klop <ronald-lists_at_klop.ws> wrote on
> Date: Fri, 10 Jan 2025 08:23:53 UTC :
> 
> > Looking at https://pkg-status.freebsd.org/builds?all=1&type=package all builds for 'default' and 13[34]releng-armv7 are failing with status 'trimming_ignore'. This started on December 15.
> > I hoped it was a glitch but it keeps happening.
> >
> > Looking at https://www.klop.ws/pkgstats/pkg-age.html it is also obvious that FreeBSD:13:armv7_latest is a bit off. :-)
> >
> > Search for 'trimming_ignore' on the pkg-status page I saw that 141releng-armv7 and main-armv7 had this issue also once or twice, but a follow-up build succeeded.
> >
> > Does anybody have an insight on the cause (and solution) of this trimming_ignore state?
> 
> 
> I'll note that the first example of this is from back on 2024-Dec-03:
> 
> default quarterly 141releng-armv7 257d1c796954 0 0 0 733 1456 -2189 trimming_ignore: Tue, 03 Dec 2024 13:31:50 GMT 00:04:34 ampere1
> 
> That is: quarterly, 14.1, on ampere1
> 
> Not being all that old, it seems to be associated with some sort of fairly recent change.
> 
> The 2024-Dec-03 failure is 41 armv7 build attempts ago (if I counted right). It is one of the 8 such failures so far. So, usually the build attempts do not get this problem. (Racy failure?)
> 
> So far, there are examples of each of:
> 
> Quarterly: 13.3, 14.1
> Latest:    13.3, 13.4, main
> 
> An implication is that all 3 of ampere[1-3] have had it happen.
> 
> So, what changed that applies to all 3 ampere* machines?
> 
> An interesting oddity is the elapsed time's ranges over the 8 failures:
> 
> Shortest: 00:04:08
> Longest:  00:17:58
> 
> But looking at which machine separately:
> 
> ampere1 (so: quarterly):
> Shortest: 00:04:08
> Longest:  00:05:41
> 
> ampere3 (so latest --but not main)
> Shortest: 00:07:56
> Longest:  00:08:42
> 
> ampere2 (just one example for main, which is an example of latest)
> Shortest: 00:17:58
> Longest:  00:17:58
> 
> ===
> Mark Millard
> marklmi at yahoo.com
>  
> 
> 
> 

 
------=_Part_3031_634390530.1737106880068
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html><head></head><body>Hi,<br>
<br>
I'm trying to get some more attention to the 'trimming_ignore' error in the pkg building cluster.<br>
<br>
See latest <a href="https://pkg-status.freebsd.org/ampere1/jail.html?mastername=141releng-armv7-quarterly" title="List builds for 141releng-armv7-quarterly">141releng-armv7-quarterly</a> failure: <a href="https://pkg-status.freebsd.org/ampere1/">https://pkg-status.freebsd.org/ampere1/</a>.<br>;
<br>
The part of the logs about this error are not public (AFAIK). So could somebody with access take a look what is happening?<br>
<br>
Regards,<br>
Ronald.<br>
<br>
&nbsp;
<p><strong>Van:</strong> Mark Millard &lt;marklmi@yahoo.com&gt;<br>
<strong>Datum:</strong> zaterdag, 11 januari 2025 04:21<br>
<strong>Aan:</strong> Ronald Klop &lt;ronald-lists@klop.ws&gt;, FreeBSD Mailing List &lt;freebsd-ports@freebsd.org&gt;<br>
<strong>Onderwerp:</strong> RE: pkg build FreeBSD:13:armv7_latest failing with trimming_ignore</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">Ronald Klop &lt;ronald-lists_at_klop.ws&gt; wrote on<br>
Date: Fri, 10 Jan 2025 08:23:53 UTC :<br>
<br>
&gt; Looking at <a href="https://pkg-status.freebsd.org/builds?all=1&amp;type=package">https://pkg-status.freebsd.org/builds?all=1&amp;type=package</a>; all builds for 'default' and 13[34]releng-armv7 are failing with status 'trimming_ignore'. This started on December 15.<br>
&gt; I hoped it was a glitch but it keeps happening.<br>
&gt;<br>
&gt; Looking at <a href="https://www.klop.ws/pkgstats/pkg-age.html">https://www.klop.ws/pkgstats/pkg-age.html</a>; it is also obvious that FreeBSD:13:armv7_latest is a bit off. :-)<br>
&gt;<br>
&gt; Search for 'trimming_ignore' on the pkg-status page I saw that 141releng-armv7 and main-armv7 had this issue also once or twice, but a follow-up build succeeded.<br>
&gt;<br>
&gt; Does anybody have an insight on the cause (and solution) of this trimming_ignore state?<br>
<br>
<br>
I'll note that the first example of this is from back on 2024-Dec-03:<br>
<br>
default quarterly 141releng-armv7 257d1c796954 0 0 0 733 1456 -2189 trimming_ignore: Tue, 03 Dec 2024 13:31:50 GMT 00:04:34 ampere1<br>
<br>
That is: quarterly, 14.1, on ampere1<br>
<br>
Not being all that old, it seems to be associated with some sort of fairly recent change.<br>
<br>
The 2024-Dec-03 failure is 41 armv7 build attempts ago (if I counted right). It is one of the 8 such failures so far. So, usually the build attempts do not get this problem. (Racy failure?)<br>
<br>
So far, there are examples of each of:<br>
<br>
Quarterly: 13.3, 14.1<br>
Latest: &nbsp;&nbsp;&nbsp;13.3, 13.4, main<br>
<br>
An implication is that all 3 of ampere[1-3] have had it happen.<br>
<br>
So, what changed that applies to all 3 ampere* machines?<br>
<br>
An interesting oddity is the elapsed time's ranges over the 8 failures:<br>
<br>
Shortest: 00:04:08<br>
Longest: &nbsp;00:17:58<br>
<br>
But looking at which machine separately:<br>
<br>
ampere1 (so: quarterly):<br>
Shortest: 00:04:08<br>
Longest: &nbsp;00:05:41<br>
<br>
ampere3 (so latest --but not main)<br>
Shortest: 00:07:56<br>
Longest: &nbsp;00:08:42<br>
<br>
ampere2 (just one example for main, which is an example of latest)<br>
Shortest: 00:17:58<br>
Longest: &nbsp;00:17:58<br>
<br>
===<br>
Mark Millard<br>
marklmi at yahoo.com<br>
&nbsp;</div>

<hr></div>
</blockquote>
<br>
&nbsp;</body></html>
------=_Part_3031_634390530.1737106880068--



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