7 Jul
2023
7 Jul
'23
11:45 p.m.
On Fri Jul 7 22:43:53 2023 +0000, **** wrote:
Marvin replied on the mailing list:
Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=134575 Your paranoid android. === w8 (32 bit report) === geolocation: geolocator.c:83: Test failed: Failed to load library, err 126. geolocator.c:86: Test failed: DllGetActivationFactory not found. === w8adm (32 bit report) === geolocation: geolocator.c:83: Test failed: Failed to load library, err 126. geolocator.c:86: Test failed: DllGetActivationFactory not found. === w864 (32 bit report) === geolocation: geolocator.c:83: Test failed: Failed to load library, err 126. geolocator.c:86: Test failed: DllGetActivationFactory not found. === w864 (64 bit report) === geolocation: geolocator.c:83: Test failed: Failed to load library, err 126. geolocator.c:86: Test failed: DllGetActivationFactory not found.
Win8 doesn't have `geolocation`, instead it has `windows.devices.geolocation` like I originally had. I adapted the tests, but am unsure how to do it properly, please advise.