Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider running test262 #3

Closed
saghul opened this issue Nov 1, 2023 · 3 comments
Closed

Consider running test262 #3

saghul opened this issue Nov 1, 2023 · 3 comments

Comments

@saghul
Copy link
Contributor

saghul commented Nov 1, 2023

There is a builtin runner. Sample run with make test2-default

151/39546/8859
Average memory statistics for 39546 tests:

QuickJS memory usage -- BigNum 2021-03-27 version, 64-bit, malloc limit: -1

NAME                    COUNT     SIZE
memory allocated          962   117824  (122.5 per block)
memory used               963   109364  (0 overhead, 8.8 average slack)
atoms                     533    21987  (41.3 per atom)
objects                   171    12349  (72.2 per object)
  properties              877    15778  (5.1 per object)
  shapes                   59    13279  (225.1 per shape)
bytecode functions         13     1549
  bytecode                 13      937  (72.1 per function)
C functions                99
arrays                      1
  fast arrays               1
  elements                  1       16  (1.0 per fast array)

Result: 151/39546 errors, 1487 excluded, 8859 skipped, 135 new, 1 changed
       72.82 real        51.04 user         6.82 sys
@bnoordhuis
Copy link
Contributor

I agree, I have it as a TODO in .github/workflows/ci.yml.

I can set it up but do you agree we don't want to vendor tc39/test262? It's pretty big (about 235 MB) so my current thinking is to git-submodule it. I hate them with a passion but it's the least worst option I can think of.

@bnoordhuis
Copy link
Contributor

#11

@saghul
Copy link
Contributor Author

saghul commented Nov 3, 2023

I agree, I have it as a TODO in .github/workflows/ci.yml.

I can set it up but do you agree we don't want to vendor tc39/test262? It's pretty big (about 235 MB) so my current thinking is to git-submodule it. I hate them with a passion but it's the least worst option I can think of.

Makes sense! Alternatively we could git clone or plain download it as part of the test process. But a submodule is the simplest for now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants