v8/test/inspector/runtime/evaluate-repl-mode-code-cache-expected.txt
Simon Zünd e281dc303e Don't use the isolate compilation cache for REPL mode scripts
The compilation cache doesn't know about REPL mode. This means that
non-REPL mode compiled scripts are successfully found for their
REPL mode equivalent and vice versa.

This CL disables the compilation cache for REPL mode scripts.
Performance is not really a concern as DevTools console inputs
are usually very small.

R=leszeks@chromium.org

Bug: chromium:1108021
Change-Id: If396c7aa004188730762e4f6bd01dae2fc141181
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2434333
Commit-Queue: Simon Zünd <szuend@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/master@{#70160}
2020-09-28 13:25:56 +00:00

25 lines
638 B
Plaintext

Tests that Runtime.evaluate's REPL mode correctly interacts with the compliation cache (crbug.com/1108021)
Prefill the cache with non-REPL mode script
{
id : <messageId>
result : {
result : {
description : 8
type : number
value : 8
}
}
}
REPL mode scripts always return a Promise.
The first script only returns "8" instead. When the inspector doesn't find a promise (due to a cache hit), it would respond with "undefined".
{
id : <messageId>
result : {
result : {
description : 8
type : number
value : 8
}
}
}