Repository navigation
Limit the build parallelism for Highway - #317
Conversation
Compiling the Highway tests runs out of virtual memory on aarch64/generic, which leaves the build in software-layer#1692 with an empty tarball. Highway gets a '*' entry that halves the cores, and keeps a quarter on A64FX, since a software entry replaces the A64FX default.
Pin software-layer-scripts to the highway-parallelism branch merged with main (EESSI/software-layer-scripts#317), to test it on aarch64/generic.
casparvl
left a comment
There was a problem hiding this comment.
We had a failed highway build in EESSI/software-layer#1692 (comment)
When using this PR, it succeeded: EESSI/software-layer#1692 (comment)
Good enough to deploy this imho.
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Hmmm, there's a hooks deploy on the way already from #342 . We should wait for that to merge, and then merge main in here, rebuild/deploy then merge here. |
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Staging PR merged |
Halves the build parallelism for Highway on every CPU target, and keeps A64FX at a quarter of the cores, which is its current default.
Compiling the Highway tests ran out of virtual memory on aarch64/generic in EESSI/software-layer#1692, which left an empty tarball.
@bedroge found it and suggested the limit.
The A64FX entry is there because a software entry in
PARALLELISM_LIMITSreplaces the per-target default, so a bare'*'entry would raise A64FX from a quarter to a half.