Bug 240767 - REGRESSION (r285418): Intl/numberformat-create-all-options.html performance test fails
Summary: REGRESSION (r285418): Intl/numberformat-create-all-options.html performance t...
Status: RESOLVED DUPLICATE of bug 242200
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-05-21 17:24 PDT by Alexey Proskuryakov
Modified: 2022-06-30 13:16 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2022-05-21 17:24:09 PDT 
https://build.webkit.org/#/builders/434/builds/840/steps/11/logs/stdio

Running Intl/numberformat-create-all-options.html (116 of 210)
ERROR: Got an exception while running test.run with name=RangeError, message=useGrouping must be either true, false, "min2", "auto", or "always"
FAILED
Finished: 0.611161 s

The last successful build was in November, https://build.webkit.org/builders?builderName=Apple-Catalina-Release-WK2-Perf&buildNumber=1974, with 243954@main. The first known unsuccessful build was with 243981@main.
Comment 1 Alexey Proskuryakov 2022-05-21 17:26:51 PDT 
Seems almost certain to have been https://commits.webkit.org/243975@main: [JSC] Implement IntlNumberFormat v3.
Comment 2 Radar WebKit Bug Importer 2022-05-21 17:26:59 PDT 
<rdar://problem/93712843>
Comment 3 Karl Rackler 2022-06-23 11:00:04 PDT 
I have skipped this test while this issue is investigated.
Comment 4 Karl Rackler 2022-06-23 11:17:43 PDT 
Pull request: https://github.com/WebKit/WebKit/pull/1731
Comment 5 EWS 2022-06-23 11:20:14 PDT 
Test gardening commit 251790@main (5e6fa1936157): <https://commits.webkit.org/251790@main>

Reviewed commits have been landed. Closing PR #1731 and removing active labels.
Comment 6 Alexey Proskuryakov 2022-06-30 13:16:54 PDT 

*** This bug has been marked as a duplicate of bug 242200 ***