All the octane tests and sunspider tests should run in new separate globals

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Won't Fix
    • Priority: P4
    • None
    • Affects Version/s: 9.1
    • Component/s: core-libs
    • None

      Right now they contaminate each other, if we use the run-octane.js harness and the runsunspider.js harness. Sunspider is especially picky, as we can't do some return value verifications with name space conflicts between benchmarks. Also notice brain dead variable names like "___i" for loop counters not to conflict with benchmark contents. This is not very sustainable.

            Assignee:
            Sundararajan Athijegannathan
            Reporter:
            Marcus Lagergren
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: