Skip to content

[BUG] Keep the harness compiling on CI runners - #22

Merged
ignaciojuarez merged 1 commit into
mainfrom
fix/harness-compile-memory
Nov 10, 2026
Merged

ignaciojuarez merged 1 commit into
mainfrom
fix/harness-compile-memory

Conversation

@ignaciojuarez

Copy link
Copy Markdown
Owner

Problem

Since #21, native-client CI fails on main. The Swift frontend is killed (signal 9) while compiling ChromiumHarnessValidation.swift. Its run function is one ~1,900-line async body. With the run body stubbed, the file needs 0.8 GB; with it, 26.6 GB. The device checks #21 added there pushed it over the runner's limit. (#19 passed at 19 minutes, already at the edge.)

Fix

Pure code motion; no check changes. Three self-contained sections leave run:

checks is passed inout, so partial results still reach failure reports. An indentation-insensitive comparison shows only the moved statements and new wrappers changed.

Validation

Before (93c1dad) After
Peak swift-frontend memory, clean debug build 26.6 GB 15.9 GB
Clean build time 156 s 52 s

python3 -m unittest, node Tests/test_smoke_fixture.mjs, swift test (34) and swift build --product CobbleChromiumClient pass. The native harness was not rerun: a foreground-only DevTools check needs the Mac's focus, which a pending macOS dialog holds. The moved code is unchanged, and the native payload is unaffected.

🤖 Generated with Claude Code

The camera/microphone device checks (#21) grew the harness's single async
validation function past what the macOS CI runner can compile: the Swift
frontend was killed (signal 9) and main's native-client check is red.

Move three self-contained sections out of `run` without changing them:
media/display/window-management requests, prompts/file choosers, and the
new device checks (HarnessMediaDeviceValidation.swift). A clean local
build's peak frontend memory drops from 26.6 GB to 15.9 GB, and build
time from 156 s to 52 s.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ignaciojuarez
ignaciojuarez merged commit 82cdefa into main Nov 10, 2026
2 checks passed
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.

1 participant