What's failing
The v8 fetch step in the core build fails deterministically:
Working on v8...
Fetching depot_tool
Fetching v8
Fetch & patch completed
Synching v8 dependencies
❌ v8 failed with code 1
-- Python script error: Aborting V8: Applying patch: gclient_paths.patch failed: error: patch failed: gclient_paths.py:162
error: gclient_paths.py: patch does not apply
CMake then aborts the whole core target:
CMake Error at common.cmake:113 (message):
Common/3dParty/build_3rdparty.py failed!
Where it's hit
chore/nightly-submodule-bump — failed 2026-07-13 and again 2026-07-17 (run 29237675047, 29565155801 on the DocumentServer side)- DocumentServer PR #262 — failed on push and again on a manual rerun (same signature both times, all 4 build matrix legs — amd64/arm64 × euro-office/nextcloud-office), confirming it's deterministic, not a transient fetch flake.
Likely cause
v8 is fetched unpinned/fresh on every build (Fetching v8 → live checkout), so this vendored patch is being applied against whatever gclient_paths.py currently looks like upstream. Upstream has apparently drifted past what the patch's context expects, so it now fails to apply on line 162 for every build, blocking anything downstream that depends on core.
Related
#72 already questions whether these v8 patches (and v8 itself, at 8.9) are still needed at all — this is a concrete instance of that fragility actually breaking builds, twice in a week. Worth deciding there whether to drop the patch, refresh it against current upstream, or pin the v8 checkout so it stops drifting under a stale patch.
What's failing
The v8 fetch step in the core build fails deterministically:
CMake then aborts the whole
coretarget:Where it's hit
chore/nightly-submodule-bump— failed 2026-07-13 and again 2026-07-17 (run 29237675047, 29565155801 on the DocumentServer side)Likely cause
v8 is fetched unpinned/fresh on every build (
Fetching v8→ live checkout), so this vendored patch is being applied against whatevergclient_paths.pycurrently looks like upstream. Upstream has apparently drifted past what the patch's context expects, so it now fails to apply on line 162 for every build, blocking anything downstream that depends oncore.Related
#72 already questions whether these v8 patches (and v8 itself, at 8.9) are still needed at all — this is a concrete instance of that fragility actually breaking builds, twice in a week. Worth deciding there whether to drop the patch, refresh it against current upstream, or pin the v8 checkout so it stops drifting under a stale patch.