-
-
Notifications
You must be signed in to change notification settings - Fork 400
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
Test262 panics #817
Comments
Updated the list of panics, counting those that are still present even after #906 gets merged. The two main areas I see for concern are the Then, we should re-check the list and make sure that all the environment related panics get solved in #659. |
I have updated the list of panics after the merges of the latest changes. It seems that our current "big thing" is |
This also implements a spec-compliant `parseInt()` function.
I have updated the list of panics. We now have one issue per panic (except for the one that happens randomly). This should help tackle the remaining Test262 panics on the Boa 0.12 release, and make it much safer to use in other projects. |
This is a full list of panics the current ECMAScript test suite (test262) gives, 13-14 in total. We should aim for 0 panics (even before we try to implement the rest of the spec):
Object already borrowed: BorrowMutError
(#1059), count: 2Identifier arguments has already been declared
(#1062), count: 8range start index 2 out of range for slice of length 0
(#1241), count: 2Could not get slice
(#1242), count: 1There is another random panic that seems to not always occur, so we don't have too much information about it, or the exact test where it happens (there are multiple tests with that name):
It seems to happen here when calling the
get_type()
function in an object, when checking if the object is a function. This happens if the object is already mutably borrowed, and this borrow will fail. Interestingly, this doesn't happen in every run.How to replicate / find code to reproduce:
If you run the test262 suite, you will be able to see for each of the panics which one was the panicking test. To run it:
This will put all panics and errors in the
error.log
file. For each panic, you will see something like this:This means that the panic was on that test file. You can search for that test file here: https://github.com/tc39/test262/find/main
The text was updated successfully, but these errors were encountered: