You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Windows: mcpp test --workspace rebuilds an up-to-date dependency module while another member has it mapped ("user-mapped section open") #936
On windows-latest, mcpp test --workspace failed twice (openmui CI runs 43561716476 and 43597284946). In both runs, a later member's build compiled a dependency's generated module again, even though an earlier member in the same run had already built it, and could not write the file:
unable to open output file 'pcm.cache/xrender.mesh.gpu/xrender.mesh.gpu-glow_shaders.pcm': The requested operation cannot be performed on a file with a user-mapped section open
(The first run had the same error with ids_shaders.pcm.) Windows won't let a file be overwritten while another process has it memory-mapped.
Expected: a dependency's module that is up to date isn't rebuilt by another member's build. If it really does need rebuilding, write to a temporary path and rename it into place, so a mapped reader never blocks the write.
Follows from #874 (the per-member rebuild cascade).
Activity
m9: the guide reads the resolved graph, a group's programs are planne…
2026.11.16.1: ecosystem gap supplement -- launchers, naming, build de…
speak-agent commentedon Nov 16, 2026
Fixed in mcpp 2026.11.16.1 (#940): a group's test programs are planned together, so a module they share is compiled once.