RESOLVED DUPLICATE of bug 269095269094
REGRESSION (274302@main): [macOS] TestWebKitAPI.SiteIsolation.DragEvents and TestWebKitAPI.SiteIsolation.PropagateMouseEventsToSubframe consistently failing
https://bugs.webkit.org/show_bug.cgi?id=269094
Summary REGRESSION (274302@main): [macOS] TestWebKitAPI.SiteIsolation.DragEvents and ...
Ryan Haddad
Reported 2024-02-09 13:54:36 PST
The following tests are consistently failing on macOS bots after https://commits.webkit.org/274302@main landed: TestWebKitAPI.SiteIsolation.DragEvents /Volumes/Data/worker/macOS-Monterey-Release-Build-EWS/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/SiteIsolation.mm:1429Expected equality of these values: 4U Which is: 4 events.count Which is: 0File name unavailableUnknown C++ exception thrown in the test body. TestWebKitAPI.SiteIsolation.PropagateMouseEventsToSubframe /Volumes/Data/worker/macOS-Monterey-Release-Build-EWS/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/SiteIsolation.mm:1384Expected equality of these values: 3U Which is: 3 eventTypes.count Which is: 2/Volumes/Data/worker/macOS-Monterey-Release-Build-EWS/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/SiteIsolation.mm:1385Expected equality of these values: "mousemove" eventTypes[0] Which is: "mousedown,40,40"/Volumes/Data/worker/macOS-Monterey-Release-Build-EWS/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/SiteIsolation.mm:1386Expected equality of these values: "mousedown,40,40" eventTypes[1] Which is: "mouseup,40,40"File name unavailableUnknown C++ exception thrown in the test body. https://build.webkit.org/#/builders/931/builds/2125/steps/19/logs/stdio https://results.webkit.org/?suite=api-tests&suite=api-tests&test=TestWebKitAPI.SiteIsolation.DragEvents&test=TestWebKitAPI.SiteIsolation.PropagateMouseEventsToSubframe
Attachments
Radar WebKit Bug Importer
Comment 1 2024-02-09 13:54:58 PST
Alexey Proskuryakov
Comment 2 2024-02-12 15:16:51 PST
TestWebKitAPI.SiteIsolation.DragEvents was a regression and got fixed in bug 269095. TestWebKitAPI.SiteIsolation.PropagateMouseEventsToSubframe was a flaky test that started to fail 100%, was also fixed, and went back to being flaky. *** This bug has been marked as a duplicate of bug 269095 ***
Note You need to log in before you can comment on or make changes to this bug.