On Wed Jun 28 21:25:19 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=134279 Your paranoid android. === w8 (32 bit report) === windows.devices.geolocation.geolocator: geolocator.c:70: Test failed: got hr 0x80004002. 0a74:geolocator: unhandled exception c0000005 at 0040104F === w8adm (32 bit report) === windows.devices.geolocation.geolocator: geolocator.c:70: Test failed: got hr 0x80004002. 09d4:geolocator: unhandled exception c0000005 at 0040104F === w864 (32 bit report) === windows.devices.geolocation.geolocator: geolocator.c:70: Test failed: got hr 0x80004002. 0ae0:geolocator: unhandled exception c0000005 at 0040104F === w864 (64 bit report) === windows.devices.geolocation.geolocator: geolocator.c:70: Test failed: got hr 0x80004002. 0af8:geolocator: unhandled exception c0000005 at 0000000000401046
Should be fixed