Build step v8:run_mksnapshot flaky on "Win" builder causing compile step to fail |
|||
Issue descriptionLatest occurrence in build #49785 [1]. This is all we see in the logs: [30309/55322] ACTION //v8:run_mksnapshot(//build/toolchain/win:x86) FAILED: gen/v8/snapshot.cc snapshot_blob.bin C:/b/depot_tools/python276_bin/python.exe ../../v8/tools/run.py ./mksnapshot --startup_src gen/v8/snapshot.cc --random-seed 314159265 --startup_blob snapshot_blob.bin I've seen it happen at least twice in since yesterday with immediate tree closure. [1] https://uberchromegw.corp.google.com/i/chromium/builders/Win/builds/49785
,
Dec 6 2016
,
Dec 6 2016
I don't think either of those is related.
,
Dec 7 2016
Build error message is: [30309/55322] ACTION //v8:run_mksnapshot(//build/toolchain/win:x86) FAILED: gen/v8/snapshot.cc snapshot_blob.bin C:/b/depot_tools/python276_bin/python.exe ../../v8/tools/run.py ./mksnapshot --startup_src gen/v8/snapshot.cc --random-seed 314159265 --startup_blob snapshot_blob.bin
,
Dec 7 2016
According to [1], this issue can be fixed if mksnapshot is robust. I filed into v8 bug [2], please use [2] for tracking. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=633159#c8 [2] https://bugs.chromium.org/p/v8/issues/detail?id=5720 mksnapshot should write temporary file then move to output file |
|||
►
Sign in to add a comment |
|||
Comment 1 by carlosk@chromium.org
, Dec 6 2016