-
Notifications
You must be signed in to change notification settings - Fork 464
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
Fix groupBy string test keys to be insertion order #4053
Conversation
This was added in #4038; ping @sosukesuzuki |
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.
confirmed these tests against my polyfill
The CI runs PRs against implementations, but only confirms that the tests can be run from beginning to end, not that they pass. (Only the ESMeta job checks if they pass.) |
7eddf30
to
3672f5d
Compare
Ahh sorry, thank you. |
See tc39/test262#4053 Bug: v8:12499 Change-Id: Ib60ed75dbd92ae1e052d76d56445c0fbad2796a6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5472808 Reviewed-by: Rezvan Mahdavi Hezaveh <[email protected]> Commit-Queue: Rezvan Mahdavi Hezaveh <[email protected]> Auto-Submit: Shu-yu Guo <[email protected]> Commit-Queue: Shu-yu Guo <[email protected]> Cr-Commit-Position: refs/heads/main@{#93510}
🥰, the first emoji, has the key
'after'
, so the insertion order of the keys is'after', 'before'
.Also, this test was committed after multiple engines have shipped
groupBy
. Did the CI run this against implementations?