-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
[Merged by Bors] - Correctly run async tests #2683
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2683 +/- ##
==========================================
+ Coverage 49.17% 49.49% +0.31%
==========================================
Files 397 393 -4
Lines 39748 39473 -275
==========================================
- Hits 19545 19536 -9
+ Misses 20203 19937 -266
... and 12 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Test262 conformance changes
Broken tests (1280):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! I think we can merge it with a bit of documentation in the new result structure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! :)
bors r+ |
So, while working on #2658 I apparently broke 1280 tests... except I didn't! Turns out we were considering async tests that didn't call the `print` function as passed tests, but the `async` section of https://github.com/tc39/test262/blob/main/INTERPRETING.md#flags says: > The test must not be considered complete until the implementation-defined print function has been invoked or some length of time has passed without any such invocation.
Pull request successfully merged into main. Build succeeded: |
So, while working on #2658 I apparently broke 1280 tests... except I didn't! Turns out we were considering async tests that didn't call the
print
function as passed tests, but theasync
section of https://github.com/tc39/test262/blob/main/INTERPRETING.md#flags says: