Bug 213786

Summary:	[GTK] Test /webkit/WebKitWebView/geolocation-permission-requests is a flaky timeout
Product:	WebKit	Reporter:	Diego Pino <dpino>
Component:	WebKitGTK	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	bugs-noreply, lmoura, mcatanzaro, vitaly
Priority:	P2
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Description Diego Pino 2020-06-30 04:31:16 PDT

See: https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Tests%29/builds/14211/steps/API%20tests/logs/stdio

ERROR:../../Tools/TestWebKitAPI/Tests/WebKitGLib/TestUIClient.cpp:808:void testWebViewMouseTarget(UIClientTest*, gconstpointer): 'webkit_hit_test_result_context_is_media(hitTestResult)' should be TRUE
  /webkit/WebKitWebView/geolocation-permission-requests:              TIMEOUT

Comment 1 Lauro Moura 2021-01-20 16:24:30 PST

In WPE it's also flaky on a daily basis since Monday, usually between between 10:00 and 16:00 (PST bot time, 18:00-00:00 UTC)

WPE Release tests: https://build.webkit.org/builders/GTK-Linux-64-bit-Release-Tests?numbuilds=50

Likely related to Mozilla rate-limiting the queries to MLS[1], as most of geoclue users seems to use the fallback geoclue API key.

What if we ask for a key specific to the WebKitGTK/WPE project to be used on the bots, regardless of waiting on debian/ubuntu package updates?

Related ubuntu issue: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290

And geoclue issue about deprecating the fallback key: https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/136


[1] https://blog.mozilla.org/services/2019/09/03/a-new-policy-for-mozilla-location-service/

Comment 2 Vitaly Dyackhov 2023-08-24 01:45:06 PDT

Seems to be fixed. See https://commits.webkit.org/267191@main