blob: 75e4798a8872417e500fc4459b813fc62bf97965 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
# Wasm Spec Tests
This directory contains scripts and configs to manage the in-tree import of the
wasm spec testsuite.
## Format of tests
Spec tests are given in `test/core` of the `spec` repository as `.wast` files.
A `.wast` file is a superset of the `.wat` format with commands for running
tests.
The spec interpreter can natively consume `.wast` files to run the tests, but
we cannot run them directly ourselves. To workaround this, we have a tool which
can convert `.wast` files to `.js` that can be run efficiently in our jit-test
harness.
## Running tests
Tests are imported to `jit-test` to be run in the JS shell.
To run under `jit-test`:
```bash
cd js/src
./jit-test.py path_to_build/dist/bin/js wasm/spec/
```
## Test importing
There are many proposals in addition to the canonical spec. Each proposal is a
fork of the canonical spec and may modify any amount of files.
This causes a challenge for any engine implementing multiple proposals, as any
proposal may conflict (and often will) with each other. This makes it
infeasible to merge all spec and proposal repos together.
Testing each proposal separately in full isn't an attractive option either, as
most tests are unchanged and that would cause a significant amount of wasted
computation time.
For this reason, we generate a set of separate test-suites that are 'pruned' to
obtain a minimal set of tests. The tool works by merging each proposal with the
proposal it is based off of and removing tests that have not changed.
### Configuration
The import tool relies on `config.toml` for the list of proposals to import,
and `config-lock.toml` for a list of commits to use for each proposal.
The lock file makes test importing deterministic and controllable. This is
useful as proposals often make inconvenient and breaking changes.
### Operation
```bash
# Add, remove, or modify proposals
vim generate-spectests/config.toml
# Remove locks for any proposals you wish to pull the latest changes on
vim generate-spectests/config-lock.toml
# Import the tests
make update
# View the tests that were imported
hg stat
# Run the imported tests and note failures
./jit-test.py dist/bin/js wasm/spec/
# Exclude test failures
vim generate-spectests/config.toml
# Re-import the tests to exclude failing tests
make update
# Commit the changes
hg commit
```
### Debugging import failures
Proposals can often have conflicts with their upstream proposals. This is okay,
and the test importer will fallback to building tests on an unmerged tree.
This will likely result in extra tests being imported due to spurious
differences between the proposal and upstream, but generally is okay.
The import tool uses `RUST_LOG` to output debug information. `Makefile`
automatically uses `RUST_LOG=info`. Change that to `RUST_LOG=debug` to get
verbose output of all the commands run.
|
