This Pull Request ignores a bunch of features in the Boa tester, since we do not implement those. The new "failures" were in fact false positives (for example, a parsing test that should fail, and it failed not because it detected wrong syntax, but because it didn't even understand it).
I wanted to bring down the "failed" tests, and I was able to do it a bit, but not quite. One feature that I noticed was failing a lot was "async-iteration". It makes around 5k tests fail, but it also makes around 6k tests work, so I guess it's just 50% implemented.
In any case, this gives a better overview on the real conformance.
This Pull Request changes the following:
- Implement `Function` constructor
- Ignore non-standard `caller` feature in 262 tests
- Fix `Function.apply` length
- Use `TypeError` in `Function.caller` and `Function.arguments` accessors
This Pull Request fixes/closes #1559.
It changes the following:
- Implement GeneratorFunction Objects
- Implement Generator Objects
- Implement generator execution in vm
- Create `FormalParameterList` to remove duplicate checks on function parameters
- Refactor `MethodDefinition` on object literals
With the implementation of `String.fromCodePoint` in #1123 some `RegExp` tests are now running for a long time. These tests check every unicode codepoint for all regexp property escape/character classes.
This not only makes the developer experience significantly worse, but also wastes cpu resources for the benefit of "completeness". I think these tests are completely useless. Ironically the unicode tables in the tests are generated - from the same data, that the unicode tables in the regex engine are also generated.
262 suite runtime:
Before: ~03:30 https://github.com/boa-dev/boa/runs/5191567446?check_suite_focus=true
After: ~31:00 https://github.com/boa-dev/boa/runs/5196405437?check_suite_focus=true
* fix(boa): fix stringpad abstract operation
- renames filter to filler in accordance with spec
- adds empty string
check to StringPad function
Closes#1306
* refactor to use `is_empty` method over comparison
* Don't consider panic fixes as "new failures"
* Improved coding style
* Fixed Test262 tester for the testing update
* Ignore JSON module tests
* Test262 uses _FIXTURE at any point of the file name
* Improved CI workflows
This improves several things in the CI workflows:
- More conformant Test262 result generation
- Benchmarks should now show comments for all users
- Added Test262 result comparison comments to Pull Requests
* Fixed typo
* Checking the comment generation
* Fixing conditions to test comments
* Fix a couple of bugs on the comparator
* Fixed format
* Trying to fix comment updating
* Removing commit autor when searching
* Replace the comment instead of appending
* Switched back to the `pull_request_target` event
raskad
Iban Eguia
LaBaguette
neeldug
tofpie