Re: why does devel/electron41 show as blacklisted on pkg.f.o

On 6/24/26 15:31, Mark Felder wrote:
> On 5/30/26 3:14 PM, [email protected] wrote:
>> On Sat, May 30, 2026 at 05:26:37PM +0200, Bugs Beastie wrote:
>>
>>> Just finished one build:
>>> [4D:08:25:51] [01] [21:03:31] Finished   devel/electron39 |
>>> electron39-39.8.10_1: Success
>>> 21 hours for electron39, this is on 4x3.3GHz core i5!
>>> [electron41 failed in a strange way in fetch/checksum phase, no data
>>> for it now]
>>
>> [07:51:54] [01] [06:04:22] Finished   devel/electron41 |
>> electron41-41.7.1: Success
>>
>> This is a from-scratch build. In other words the poudriere builder was
>> cleaned
>> with poudriere pkgclean -A -j jailname.
>>
>> The build was started with 'doas poudriere bulk -j 151amd64 -J16
>> devel/electron4'
>>
>> System is
>>
>> Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz / 384GB RAM hw.ncpu=16 SHT=off
>>
>> ccache4 is in use.
>>
> 
> Just want to chime in that I build electron all the time and never see
> such crazy long build times.
> 
> hw.model: AMD Ryzen 9 5900X 12-Core Processor
> hw.physmem: 137276297216
> 
> poudriere.conf:
> 
> USE_TMPFS=no
> ALLOW_MAKE_JOBS=yes
> CCACHE_DIR=/ccache
> 
> the result:
> 
> ===>  Cleaning for electron42-42.3.3
> build of devel/electron42 | electron42-42.3.3 ended at Sun Jun 14
> 09:09:20 UTC 2026
> build time: 02:17:09

Do you allow a bunch of other port package builds to potentially be
running in parallel?

The problem to solve for an official port package builder machine's bulk
build(s) spans sometimes handling building over 35000 port packages in
one run, to be distributed together, not just a few hundred. Avoiding
running out of resources and, so, avoiding more build failures is part
of that.

> 
> 
> This is a CPU from 6 years ago. It's not even something good like an
> EPYC with 192 cores...
> 
> 
> 
> Mark
> 
> 


-- 
===
Mark Millard
marklmi at yahoo.com