Bug 205956

Summary: REGRESSION: (r253718) [ Mac ] inspector/runtime/executionContextCreated-onEnable.html is a flaky failure
Product: WebKit Reporter: Truitt Savell <tsavell>
Component: Web InspectorAssignee: Yury Semikhatsky <yurys>
Status: NEW    
Severity: Normal CC: commit-queue, hi, inspector-bugzilla-changes, webkit-bot-watchers-bugzilla, webkit-bug-importer, yurys
Priority: P1 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Truitt Savell
Reported 2020-01-08 14:14:26 PST
inspector/runtime/executionContextCreated-onEnable.html Description: This test was introduced in https://trac.webkit.org/changeset/253718/webkit and have been flaky sense then History: https://results.webkit.org/?suite=layout-tests&test=inspector%2Fruntime%2FexecutionContextCreated-onEnable.html Diff: --- /Volumes/Data/slave/catalina-release-tests-wk1/build/layout-test-results/inspector/runtime/executionContextCreated-onEnable-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk1/build/layout-test-results/inspector/runtime/executionContextCreated-onEnable-actual.txt @@ -5,7 +5,12 @@ == Running test suite: Runtime.executionContextCreated.OnEnable -- Running test case: Runtime.executionContextCreated.OnEnable.NoDuplicates Execution context created: id=0 frameId=0 isPageContext=true -Execution context created: id=1 frameId=1 isPageContext=true -PASS: Should receive 2 executionContextCreated events (for main world in the main frame and the subframe). -PASS: Should have 2 unique contexts. +Execution context created: id=1 frameId=0 isPageContext=false +Execution context created: id=2 frameId=1 isPageContext=true +FAIL: Should receive 2 executionContextCreated events (for main world in the main frame and the subframe). + Expected: 2 + Actual: 3 +FAIL: Should have 2 unique contexts. + Expected: 2 + Actual: 3
Attachments
Radar WebKit Bug Importer
Comment 1 2020-01-08 14:14:59 PST
Alexey Proskuryakov
Comment 2 2020-01-11 18:09:32 PST
*** Bug 206130 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.