Bug 1642708 - Remove generated BinAST tests. r=arai CLOSED TREE

Remove the following directories:
  js/src/jsapi-tests/binast/
  js/src/jit-test/tests/binast/

These tests were largely auto-generated and can be reproduced in the future
using an updated encoder.
This commit is contained in:
Ted Campbell 2020-06-17 18:37:44 -04:00
parent bbe92cb7fa
commit 46b9b28572
9253 changed files with 0 additions and 39456 deletions

View File

@ -1,45 +0,0 @@
# BinAST encoded jit-test
Files inside `lazy` and `nonlazy` directories are encoded from the
corresponding plain JS files.
`lazy` directory contains BinAST files that mark every functions "lazy",
so that those functions are compiled lazily.
`nonlazy` directory contains BinST files that mark every functions "eager",
so that those functions are compiled eagerly.
See js/src/jsapi-tests/binast/README.md for more details how to encode or
update them.
# Run BinAST encoded jit-test
By default, BinAST encoded jit-test files are skipped for automation
reason (to avoid consuming much time on non linux64 env)
Passing `--run-binast` parameter to `jit_test.py` enables them.
```
./jit_test.py {PATH_TO_SHELL} --run-binast
```
To run specific BinAST encoded files, specify the path to the BinAST files
just like plain JS file's case.
```
./jit_test.py {PATH_TO_SHELL} --run-binast {PATH_TO_BINAST_FILES}
```
# Run BinAST encoded jit-test on try
On automation, BinAST encoded jit-test files are executed only on the
following jobs:
- linux64 opt SM(p)
- linux64 debug SM(p)
- linux64 debug SM(cgc)
For more details, see `conditional-env` property in
js/src/devtools/automation/variants/{plain,plaindebug,compacting} files.

View File

@ -1 +0,0 @@
// |jit-test| error: unlabeled break must be inside loop or switch

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error: continue must be inside loop

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error: Empty string

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error: label not found

View File

@ -1 +0,0 @@
// |jit-test| error: continue must be inside loop

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:SyntaxError

View File

@ -1 +0,0 @@
// |jit-test| error:TypeError

View File

@ -1 +0,0 @@
// |jit-test| error:Error

View File

@ -1 +0,0 @@
|jit-test| skip-if: !this.hasOwnProperty("TypedObject")

View File

@ -1 +0,0 @@
// |jit-test| error:Error

View File

@ -1 +0,0 @@
// |jit-test| error:Error

View File

@ -1 +0,0 @@
// |jit-test| error:Error;

View File

@ -1 +0,0 @@
// |jit-test| error:TypeError

View File

@ -1 +0,0 @@
// |jit-test| error:Error

View File

@ -1 +0,0 @@
// |jit-test| error: TypeError

Some files were not shown because too many files have changed in this diff Show More