387148 - Add js/benchmarks suite to talos

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect, P3)

Description

[Mike Schroepfer]

There are a bunch of tests and benchmarks hidden in CVS.  We should take the ones that are performance oriented, make sure they are sane, and add them to Talos so we can get them run on a regular basis.

Comment 1

[Mike Schroepfer]

See URL for location of files.

Comment 2

[alice nodelman [:alice] [:anode]]

For Talos integration we'd need to:

* have each test loadable as an url
* have each test dump it's results wrapped in '__start_report*__end_report'.  I'm assuming that the value outputted by each test is simply a number in ms, so it can work on the same system as Ts currently runs.
* have the test close the browser (using quit.js so to work on Mac) upon test completion or output '__FAIL*__FAIL' with an appropriate error message.

Are we interested in collecting any other information while these tests are running?  Memory footprint?  CPU usage (currently windows only)?

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Alice: can you sanity check what tests are still in CVS, and worth adding to Talos?

Comment 4

[alice nodelman [:alice] [:anode]]

I really wouldn't be the best resource for deciding if these tests are still worth running.  We already run dromaeo and sunspider, maybe we could get a developer working on the js engine to look these over to see if there is something that we are missing?

Comment 5

[alice nodelman [:alice] [:anode]]

Without more context here as to which specific tests we want and how we want them run, closing as INCOMPLETE.

Comment 6

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.