v8/test/inspector/debugger/cleanup-old-failed-to-parse-anonymous-scripts-expected.txt

Checks that inspector collects old faied to parse anonymous scripts.
Generate 1000 scriptFailedToParse events
error:0
success:1000
Generate three scriptFailedToParse event for non anonymous script
error:0
success:1003
Generate one more scriptFailedToParse event for anonymous script
error:100
success:904
Check that latest script is still available
{
    id : <messageId>
    result : {
        scriptSource : }
    }
}
[inspector] cleanup old failed to parse anonymous scripts We already cleanup these scripts on frontend side. It is crucial to cleanup them on backend side as well, since some web applications use following logic: get some data from network, add this data to buffer, try to parse buffer using JSON.parse. On each unsuccessfull JSON.parse we get another scriptFailedToParse event. Frontend logic of discarding scripts: https://goo.gl/FDtaWK Some idea of smarter logic here: track what script ids are reported using protocol and cleanup only script ids which reported not only as part of scriptFailedToParse event. R=alph@chromium.org Bug: chromium:810812 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ifd67764c232e4abc7dc6e8e69a651bf9ac0e381b Reviewed-on: https://chromium-review.googlesource.com/919834 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#51337} 2018-02-16 20:06:30 +00:00			`Checks that inspector collects old faied to parse anonymous scripts.`
			`Generate 1000 scriptFailedToParse events`
			`error:0`
			`success:1000`
			`Generate three scriptFailedToParse event for non anonymous script`
			`error:0`
			`success:1003`
			`Generate one more scriptFailedToParse event for anonymous script`
			`error:100`
			`success:904`
			`Check that latest script is still available`
			`{`
			`id : <messageId>`
			`result : {`
			`scriptSource : }`
			`}`
			`}`