Bug 208905

Summary: Flaky Test: imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: WebCore JavaScriptAssignee: WebKit Commit Bot <commit-queue>
Status: NEW ---    
Severity: Normal CC: ap, cdumez, Ms2ger, rniwa, youennf, ysuzuki
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 50856    
Attachments:
Description Flags
Archive of layout-test-results from webkit-cq-03 none

Description WebKit Commit Bot 2020-03-10 21:50:51 PDT
This is an automatically generated bug from the commit-queue.
imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html has been flaky on the commit-queue.

imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html was authored by ms2ger@igalia.com and youennf@gmail.com.
https://trac.webkit.org/browser/trunk/LayoutTests/imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html

The commit-queue just saw imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html flake (text diff) while processing attachment 393185 [details] on bug 208892.
Bot: webkit-cq-03  Port: <class 'webkitpy.common.config.ports.MacPort'>  Platform: Mac OS X 10.14.6

The bots will update this with information from each new failure.

If you believe this bug to be fixed or invalid, feel free to close.  The bots will re-open if the flake re-occurs.

If you would like to track this test fix with another bug, please close this bug as a duplicate.  The bots will follow the duplicate chain when making future comments.
Comment 1 WebKit Commit Bot 2020-03-10 21:50:52 PDT
Created attachment 393206 [details]
Archive of layout-test-results from webkit-cq-03
Comment 2 Alexey Proskuryakov 2020-03-11 09:46:21 PDT
This is a rare failure on post-commit bots.

-PASS Constructed GamepadEvent timestamp should be high resolution and have the same time origin as performance.now() 
+FAIL Constructed GamepadEvent timestamp should be high resolution and have the same time origin as performance.now() undefined is not a constructor (evaluating 'new window[eventType]('test')')

Looks like a garbage collection bug?