Optimize the js
package test by using compatibility mode base
#1426
Labels
Milestone
js
package test by using compatibility mode base
#1426
For the most part most test execute extremely simple 1-2 line scripts which can be rewritten to not require babel or corejs and at this point run in
compatibility-mode=base
.This shouldn't really be a problem for finding bugs in the extended mode, but maybe I am wrong.
As an example, I give
TestVURunInterruptDoesntPanic
, which is probably not the most representative, but still. The below are the first and second run of the same test (using -count):without specifying compatibility-mode:base:
after speciying:
as you can see the difference is signifacant as the parsing of the code apperantly takes 10.5s more without specifying
base
and the execution combined takes like 0.5s less (the number vary but not more then 0.1s in my experiments).All of the above is ran with
-race
and the code change is:The text was updated successfully, but these errors were encountered: