From: Radek Doulik Date: Wed, 5 Apr 2023 16:10:52 +0000 (+0200) Subject: [wasm] Freeze the emscripten cache (#84356) X-Git-Tag: accepted/tizen/unified/riscv/20231226.055536~3117 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=da7fbb7668d3cba3f2995675c6e8f0ad38caa8cd;p=platform%2Fupstream%2Fdotnet%2Fruntime.git [wasm] Freeze the emscripten cache (#84356) This fixes https://github.com/dotnet/runtime/issues/83655 We prime the cache before packaging the emsdk cache package and also in docker images, so we don't need to update the cache, which might be in read-only location anyway. The underlying issue was problem with the cache lock: "C:/helix/work/correlation/build/emsdk/upstream/bin\clang.exe" --version cache:WARNING: Accessing the Emscripten cache at "C:\helix\work\correlation\build\emsdk\upstream\emscripten\cache" (for "sanity") is taking a long time, another process should be writing to it. If there are none and you suspect this process has deadlocked, try deleting the lock file "C:\helix\work\correlation\build\emsdk\upstream\emscripten\cache\cache.lock" and try again. If this occurs deterministically, consider filing a bug. cache:WARNING: Accessing the Emscripten cache at "C:\helix\work\correlation\build\emsdk\upstream\emscripten\cache" (for "sanity") is taking a long time, another process should be writing to it. If there are none and you suspect this process has deadlocked, try deleting the lock file "C:\helix\work\correlation\build\emsdk\upstream\emscripten\cache\cache.lock" and try again. If this occurs deterministically, consider filing a bug. --- diff --git a/src/mono/wasm/build/WasmApp.Native.targets b/src/mono/wasm/build/WasmApp.Native.targets index 0a0c3f6..15c8143 100644 --- a/src/mono/wasm/build/WasmApp.Native.targets +++ b/src/mono/wasm/build/WasmApp.Native.targets @@ -255,6 +255,7 @@ +