02cb54e3cc
Instead, make it possible for indifidual tests to pass "always true flags" which are not part of the varying flag set. The downside is that if an experimental flag changes parsing of some of the unrelated code snippets, it's noticed later (only after the flag is turned on by default). But this is a reasonable trade off for faster tests. Additional fix: Some tests (ErrorsFutureStrictReservedWords) were using always_flags incorrectly (running two different tests with different always_flags basically iterates over every flag combination anyway - most of them twice). BUG=v8:3707 LOG=N Review URL: https://codereview.chromium.org/772823002 Cr-Commit-Position: refs/heads/master@{#25628} |
||
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
intl | ||
js-perf-test | ||
message | ||
mjsunit | ||
mozilla | ||
preparser | ||
promises-aplus | ||
test262 | ||
test262-es6 | ||
unittests | ||
webkit |