Skip to content

Reduce macOS LLVM build parallelism to avoid compiler segfaults#5100

Merged
SeanTAllen merged 1 commit intomainfrom
reduce-macos-build-parallelism
Apr 2, 2026
Merged

Reduce macOS LLVM build parallelism to avoid compiler segfaults#5100
SeanTAllen merged 1 commit intomainfrom
reduce-macos-build-parallelism

Conversation

@SeanTAllen
Copy link
Copy Markdown
Member

Apple Clang on the macos-26 runners has been segfaulting during LLVM lib builds (Segmentation fault: 11 in clang++), causing repeated CI failures on both Intel and ARM64 macOS jobs starting around April 1.

The Intel runners only have 4 cores, so -j8 was double the core count and likely causing memory pressure. ARM64 runners have 10 cores but the LLVM translation units being compiled are very memory-heavy.

This reduces parallelism to -j2 for Intel (macos-26-intel) and -j4 for ARM64 (macos-26). Linux and Docker jobs remain at -j8.

Apple Clang on the macos-26 runners has been segfaulting during LLVM
builds, likely due to memory pressure from too many parallel compilation
jobs. Intel runners have 4 cores and ARM64 runners have 10 cores, so
-j8 was particularly aggressive for Intel. Reduce to -j2 for Intel and
-j4 for ARM64.
@ponylang-main ponylang-main added the discuss during sync Should be discussed during an upcoming sync label Apr 2, 2026
@SeanTAllen
Copy link
Copy Markdown
Member Author

This is a pure shot in the dark but we keep dying and failing and segfaulting the last couple days building LLVM on macos runners. We have other failures as well running the stress tests that are "vm went away" so this might not be a valid fix or it might be that something changed with runners and it is causing multiple problems.

@SeanTAllen SeanTAllen merged commit 7f7aa0a into main Apr 2, 2026
22 checks passed
@SeanTAllen SeanTAllen deleted the reduce-macos-build-parallelism branch April 2, 2026 17:06
@ponylang-main ponylang-main removed the discuss during sync Should be discussed during an upcoming sync label Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants