Fabian 719bc39e08 fix more AMD-specific undefined behaviour | 1 year ago | |
---|---|---|
.. | ||
api | 1 year ago | |
benchmark | 1 year ago | |
devices | 1 year ago | |
expect | 2 years ago | |
full | 1 year ago | |
jit-paging | 1 year ago | |
kvm-unit-tests | 1 year ago | |
manual | 1 year ago | |
nasm | 1 year ago | |
qemu | 1 year ago | |
rust | 3 years ago | |
Readme.md | 3 years ago |
Use the corresponding make
target in the root directory to run a test. The
following list is roughtly sorted from most interesting/useful to least.
The following environmental variables are respected by most tests if applicable:
TEST_RELEASE_BUILD=1
: Test the release build (libv86.js, v86.wasm) instead of the
debug build (libv86-debug.js, v86-debug.wasm)MAX_PARALLEL_TESTS=n
: Maximum number of tests to run in parallel. Defaults
to the number of cores in your system or less.TEST_NAME="…"
: Run only the specified test (only expect, full, nasm)