heavybuilder request for nodejs-electron #13545

Closed
opened 2026-09-05 04:07:40 +00:00 by gordonmessmer · 8 comments

Description of request

A new "nodejs-electron" package, derived from the chromium package and similar to cef, will be added to Fedora. The dist-git has been provisioned, but scratch builds fail (OOM).

Please add this package to the heavy builders.

### Description of request A new "nodejs-electron" package, derived from the chromium package and similar to cef, will be added to Fedora. The dist-git has been provisioned, but scratch builds fail (OOM). Please add this package to the heavy builders.
Owner

Ugh. Another one. ;(

Does this build on s390x? or just other arches?

Ugh. Another one. ;( Does this build on s390x? or just other arches?
Author

ExclusiveArch: x86_64 aarch64

ExclusiveArch: x86_64 aarch64

Technically it should be able to build on ppc64le too, since chromium does. So only s390x is excluded.

Technically it should be able to build on ppc64le too, since chromium does. So only s390x is excluded.
Author

I mean... we could try ppc64le, but I would consider such a build experimental since the electron project does not test or release for that platform. (AFAICT)

What is the CPU core count and memory profile of a heavy builder?

I mean... we could try ppc64le, but I would consider such a build experimental since the electron project does not test or release for that platform. (AFAICT) What is the CPU core count and memory profile of a heavy builder?

@gordonmessmer wrote in #13545 (comment):

I mean... we could try ppc64le, but I would consider such a build experimental since the electron project does not test or release for that platform. (AFAICT)

That's true, though we do have desktop users on Power Systems (mostly Talos folks and whatnot). That's why they've contributed the support to Fedora's chromium packages to support it.

What is the CPU core count and memory profile of a heavy builder?

At least with the x86_64 ones, it's 64 cores and 128GB of RAM. For AArch64, it's 80 cores and 384GB of RAM. I don't think we have heavy builders for ppc64le.

@gordonmessmer wrote in https://forge.fedoraproject.org/infra/tickets/issues/13545#issuecomment-1353784: > I mean... we could try ppc64le, but I would consider such a build experimental since the electron project does not test or release for that platform. (AFAICT) > That's true, though we do have desktop users on Power Systems (mostly Talos folks and whatnot). That's why they've contributed the support to Fedora's chromium packages to support it. > What is the CPU core count and memory profile of a heavy builder? At least with the x86_64 ones, it's 64 cores and 128GB of RAM. For AArch64, it's 80 cores and 384GB of RAM. I don't think we have heavy builders for ppc64le.
Author

At least with the x86_64 ones, it's 64 cores and 128GB of RAM. For AArch64, it's 80 cores and 384GB of RAM. I don't think we have heavy builders for ppc64le.

This is probably the wrong place to discuss it, but we should probably set tasksize for chromium and derived packages so that it's usually possible to build without a heavy builder:

# Require 4 GB of RAM per CPU core
%global _smp_tasksize_proc 2048

_smp_tasksize_proc defaults to just 512M. Increasing it to 2G shouldn't make the build any slower on the heavy builders, but might allow it to succeed on more non-heavy builders.

> At least with the x86_64 ones, it's 64 cores and 128GB of RAM. For AArch64, it's 80 cores and 384GB of RAM. I don't think we have heavy builders for ppc64le. This is probably the wrong place to discuss it, but we should probably set tasksize for chromium and derived packages so that it's usually possible to build without a heavy builder: ``` # Require 4 GB of RAM per CPU core %global _smp_tasksize_proc 2048 ``` _smp_tasksize_proc defaults to just 512M. Increasing it to 2G shouldn't make the build any slower on the heavy builders, but might allow it to succeed on more non-heavy builders.
kevin self-assigned this 2026-09-08 16:30:44 +00:00
Owner

At least with the x86_64 ones, it's 64 cores and 128GB of RAM. For AArch64, it's 80 cores and 384GB of RAM. I don't think we have heavy builders for ppc64le.

Well, no, it's variable for x86_64 at least. cpus:

buildhw-x86-03.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 64
buildhw-x86-04.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 64
buildhw-x86-05.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 112
buildhw-x86-06.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 112
buildhw-x86-07.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 64
buildhw-x86-08.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 32
buildhw-x86-09.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 32
buildhw-x86-10.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 192
buildhw-x86-11.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 192
buildhw-x86-12.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 32
buildhw-x86-13.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 192
buildhw-x86-14.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48
buildhw-x86-15.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48
buildhw-x86-16.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48
buildhw-x86-17.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48

But all of those are more than the defaul buildvm's by a long way.

> At least with the x86_64 ones, it's 64 cores and 128GB of RAM. For AArch64, it's 80 cores and 384GB of RAM. I don't think we have heavy builders for ppc64le. Well, no, it's variable for x86_64 at least. cpus: buildhw-x86-03.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 64 buildhw-x86-04.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 64 buildhw-x86-05.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 112 buildhw-x86-06.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 112 buildhw-x86-07.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 64 buildhw-x86-08.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 32 buildhw-x86-09.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 32 buildhw-x86-10.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 192 buildhw-x86-11.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 192 buildhw-x86-12.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 32 buildhw-x86-13.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 192 buildhw-x86-14.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48 buildhw-x86-15.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48 buildhw-x86-16.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48 buildhw-x86-17.rdu3.fedoraproject.org | CHANGED | rc=0 | (stdout) 48 But all of those are more than the defaul buildvm's by a long way.
Owner

This is now done. Let us know if you have any issues.

This is now done. Let us know if you have any issues.
kevin closed this issue 2026-09-08 20:58:28 +00:00
Sign in to join this conversation.
No milestone
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/tickets#13545
No description provided.