v8/test/message/wasm-module-name-streaming.out

RuntimeError: unreachable
    at test-module (wasm-function[0]:1)
    at pair (test/message/wasm-module-name-async.js:19:27)
    at promise.then.result (test/mjsunit/mjsunit.js:*)
[wasm] Load module name during streaming compile The streaming compilation pipeline did not parse the names section and this is also not longer needed for getting function or local names. However, the module name still needs to be set eagerly. Change-Id: I1ac12e98b970ea0781302dc44ee684510bdf2d69 Reviewed-on: https://chromium-review.googlesource.com/962452 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Stephan Herhut <herhut@chromium.org> Cr-Commit-Position: refs/heads/master@{#51979} 2018-03-15 12:57:50 +00:00			`RuntimeError: unreachable`
			`at test-module (wasm-function[0]:1)`
			`at pair (test/message/wasm-module-name-async.js:19:27)`
[cleanup] Don't bake mjsunit.js line numbers into message tests. Whenever mjsunit.js changes, these tests might suddenly fail. R=herhut@chromium.org Bug: v8:7570 Change-Id: Ib43b03a3df92a4c5acabc193c63f46b29ea992b0 Reviewed-on: https://chromium-review.googlesource.com/1032440 Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#52839} 2018-04-27 09:33:10 +00:00			`at promise.then.result (test/mjsunit/mjsunit.js:*)`