Bug 149003

Summary: [Mac] Promise resolved callback should be called before a setTimeout callback
Product: WebKit Reporter: Xabier Rodríguez Calvar <calvaris>
Component: New BugsAssignee: Xabier Rodríguez Calvar <calvaris>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: benjamin, buildbot, darin, ggaren, rniwa, sam
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
URL: https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9
Attachments:
Description Flags
Test
buildbot: commit-queue-
Archive of layout-test-results from ews104 for mac-mavericks-wk2 none

Description Xabier Rodríguez Calvar 2015-09-09 08:57:29 PDT
[Mac] Promise resolved callback should be called before a setTimeout callback
Comment 1 Xabier Rodríguez Calvar 2015-09-09 08:58:15 PDT
Created attachment 260861 [details]
Test

It seems that according to the spec https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9 the callback of a resolved promise should be called before a setTimeout(..., 0). This test works in GTK+ but fails in Mac.
Comment 2 Xabier Rodríguez Calvar 2015-09-09 09:03:51 PDT
I don't know where the problem is, but at least I provided the test.
Comment 3 Build Bot 2015-09-09 10:32:03 PDT
Comment on attachment 260861 [details]
Test

Attachment 260861 [details] did not pass mac-wk2-ews (mac-wk2):
Output: http://webkit-queues.webkit.org/results/154824

New failing tests:
js/dom/Promise-resolved-vs-timeout.html
Comment 4 Build Bot 2015-09-09 10:32:07 PDT
Created attachment 260863 [details]
Archive of layout-test-results from ews104 for mac-mavericks-wk2

The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews.
Bot: ews104  Port: mac-mavericks-wk2  Platform: Mac OS X 10.9.5
Comment 5 Sam Weinig 2015-09-09 15:52:41 PDT
I think this is just a duplicate of https://bugs.webkit.org/show_bug.cgi?id=147933. I have a patch up to fix it but it is still failing one Stream test. I would love if someone could take a look at the failing test.

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