[Test] Reconfigure SuperSpread benchmarks to run in separate processes.

test/js-perf-test/SixSpeed.json

 {
   "name": "SixSpeed",
   "run_count": 3,
   "run_count_arm": 1,
   "run_count_arm64": 1,
   "timeout": 120,
   "units": "score",
   "total": true,
   "resources": ["base.js"],
   "tests": [
@@ skipping 36 matching lines @@
       "results_regexp": "^%s\\(Score\\): (.+)$",
       "tests": [
         {"name": "Spread-ES5"},
         {"name": "Spread-Traceur"},
         {"name": "Spread-ES6"}
       ]
     },
     {
       "name": "SuperSpread",
       "path": ["SixSpeed/super_spread"],
-      "main": "run.js",
-      "resources": [
-        "run.js",
-        "super_spread.js"
-      ],
       "flags": ["--future"],
       "results_regexp": "^%s\\(Score\\): (.+)$",

[Michael Achenbach, 2017/02/02 14:50:19]

Did you check locally that this works? It can be that the regexp needs to move a
level lower with the %s replaced with the actual name.

[petermarshall, 2017/02/03 09:54:35]

Yes it runs locally and produces the correct JSON.

       "tests": [
-        {"name": "SuperSpread-ES5"},
-        {"name": "SuperSpread-Babel"},
-        {"name": "SuperSpread-ES6"}
+        {
+          "name": "ES5",

[Michael Achenbach, 2017/02/02 14:50:19]

You could also reuse the same run.js and pass a different flag to it for each
benchmark. You can use the test_flags key for that.

[petermarshall, 2017/02/03 09:54:35]

That is awesome, I was wondering if there was something like that. Done!

+          "main": "es5.js"
+        },
+        {
+          "name": "Babel",
+          "main": "babel.js"
+        },
+        {
+          "name": "ES6",
+          "main": "es6.js"
+        }
       ]
     }
   ]
 }