| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add C++ compiler and flags to the target
and build executor with the C++ compiler.
This will be needed to merge syz-fuzzer in to syz-executor
since it will be beefier and will most likely require linking in libc++.
But also this should fix #4821 since we won't use C++ flags
when building C sources (we already had work-around in pkg/csource,
but not in syz-extract).
Fixes #4821
|
| |
|
|
|
|
|
|
|
|
| |
Github actions VMs have 2 vCPUs (Standard_DS2_v2 class). So we don't get lots of speed up
from make parallelism, but we are getting memory oversubscription and duplicated work
because make invokes multiple go commands that potentially build same packages in parallel.
Go command itself parallelizes compiler and test invocations. So disable make parallelism
to avoid OOM kills.
Update #2886
|
| |
|
|
|
|
|
| |
We previously observed syz-bot hanging OpenBSD machines. We made the
problem less acute by throwing resources at it. Go builds are good at
exploiting the machines themselves, so limiting make concurrency is a
clear benefit on OpenBSD.
|
| |
|
|
|
|
|
|
|
|
| |
Ensure that we have at least 1GB per Go compiler/linker invocation.
Go compiler/linker can consume significant amount of memory
(observed to consume at least 600MB). See #1276 for context.
And we have parallelization both on make and on go levels,
this can severe oversubscribe RAM.
Note: the result can be significantly lower than the CPU number,
but this is fine because Go builds/tests are parallelized internally.
|
|
|
syz-env will be a good, short name for the planned
docker-ized build environment. So rename syz-env to syz-make.
Maybe not the best name, but it's not visible basically anywhere.
|
