Bug 225258

Summary: js/dom/Promise-reject-large-string.html is a flaky failure
Product: WebKit Reporter: Truitt Savell <tsavell>
Component: WebCore JavaScriptAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: jenner, mark.lam, saam, tzagallo, webkit-bot-watchers-bugzilla, webkit-bug-importer, ysuzuki
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=223777
https://bugs.webkit.org/show_bug.cgi?id=242812

Truitt Savell
Reported 2021-04-30 16:20:05 PDT
js/dom/Promise-reject-large-string.html I am seeing this more frequently on Apple Silicon systems History: https://results.webkit.org/?suite=layout-tests&test=js%2Fdom%2FPromise-reject-large-string.html Diff: --- /Volumes/Data/worker/bigsur-release-applesilicon-tests-wk2/build/layout-test-results/js/dom/Promise-reject-large-string-expected.txt +++ /Volumes/Data/worker/bigsur-release-applesilicon-tests-wk2/build/layout-test-results/js/dom/Promise-reject-large-string-actual.txt @@ -1,4 +1,3 @@ -CONSOLE MESSAGE: Unhandled Promise Rejection: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa... PASS successfullyParsed is true TEST COMPLETE
Attachments
Radar WebKit Bug Importer
Comment 1 2021-04-30 16:20:47 PDT
Truitt Savell
Comment 2 2021-04-30 16:21:17 PDT
Truitt Savell
Comment 3 2021-04-30 16:34:44 PDT
I was able to reproduce this test using command: run-webkit-tests --iterations 2000 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --debug-rwt-logging --no-retry --force --no-build -f js/dom/Promise-reject-large-string.html
Robert Jenner
Comment 4 2021-05-11 11:06:06 PDT
Adding test expectations Pass Failure here while test is reviewed: https://trac.webkit.org/changeset/277333/webkit
Alexey Proskuryakov
Comment 5 2022-07-15 16:45:00 PDT
This is still happening, close to 100% of the time.
Note You need to log in before you can comment on or make changes to this bug.