v8/tools/unittests/testdata
Michael Achenbach 98cde3f400 [test] Expose test-framework name in test results
This will allow to distinguish between the standard runner and the num fuzzer
on the infra side when generating flako command lines. The value could be
inferred, but it'd be more confusing.

Bug: v8:8971
Change-Id: I78f5104135d1c7fd7d98bceb4b17897e79421455
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1564050
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: Sergiy Belozorov <sergiyb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#60769}
2019-04-11 11:34:53 +00:00
..
testroot1 [test] Skip test with gcc build 2019-02-27 14:46:02 +00:00
testroot2 [test] Skip test with gcc build 2019-02-27 14:46:02 +00:00
d8_mocked1.py Preparing v8 to use with python3 /tools 2019-02-19 09:12:07 +00:00
d8_mocked2.py Preparing v8 to use with python3 /tools 2019-02-19 09:12:07 +00:00
expected_test_results1.json [test] Expose test-framework name in test results 2019-04-11 11:34:53 +00:00
expected_test_results2.json [test] Expose test-framework name in test results 2019-04-11 11:34:53 +00:00
predictable_mocked.py Preparing v8 to use with python3 /tools 2019-02-19 09:12:07 +00:00
results_processor.py Preparing v8 to use with python3 /tools 2019-02-19 09:12:07 +00:00
test1.json [tools] Detect location of android build tools automatically 2018-07-25 11:23:55 +00:00
test2.json [tools] Detect location of android build tools automatically 2018-07-25 11:23:55 +00:00
test3.json [tools] Detect location of android build tools automatically 2018-07-25 11:23:55 +00:00