cf4adddbfa
protocol::HashMap(std::unordered_map)::iterator doesn't provide any guarantees about iteration order. At least Visual C++ from vS 2015 and clang compile for loop inside forEachSession differently. For tests we need stable order of iteration, so let's use std::map instead. R=dgozman@chromium.org Bug: none Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: I329cb24cd182baa86c0ea4a526257856718f32b1 Reviewed-on: https://chromium-review.googlesource.com/609489 Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#47281} |
||
|---|---|---|
| .. | ||
| create-session-expected.txt | ||
| create-session.js | ||
| debugger-stepping-and-breakpoints-expected.txt | ||
| debugger-stepping-and-breakpoints.js | ||
| pause-on-console-assert-expected.txt | ||
| pause-on-console-assert.js | ||
| runtime-command-line-api-expected.txt | ||
| runtime-command-line-api.js | ||
| runtime-console-api-called-expected.txt | ||
| runtime-console-api-called.js | ||
| runtime-evaluate-exception-expected.txt | ||
| runtime-evaluate-exception.js | ||
| runtime-evaluate-expected.txt | ||
| runtime-evaluate.js | ||
| runtime-remote-object-expected.txt | ||
| runtime-remote-object.js | ||