Re: [PATCH v2 0/13] MR1447: mshtml: Implement performance.timing timestamps properly.

[Gabriel Ivăncescu (＠insn)]

On Sat Nov 19 19:56:44 2022 +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=126479
> Your paranoid android.
> === w10pro64_ar (64 bit report) ===
> mshtml:
> htmldoc.c:351: Test failed: expected Exec_SETTITLE
> htmldoc.c:3019: Test failed: unexpected call Exec_SETTITLE
> === w10pro64_ja (64 bit report) ===
> mshtml:
> htmldoc.c:1121: Test failed: L"domInteractive" is 0
> === debian11 (32 bit report) ===
> d3d9:
> stateblock: Timeout
> visual: Timeout
> d3dcompiler_43:
> asm: Timeout
> blob: Timeout
> hlsl_d3d11: Timeout
> hlsl_d3d9: Timeout
> reflection: Timeout
> d3dcompiler_46:
> asm: Timeout
> blob: Timeout
> hlsl_d3d11: Timeout
> hlsl_d3d9: Timeout
> reflection: Timeout
> d3dcompiler_47:
> asm: Timeout
> blob: Timeout
> hlsl_d3d11: Timeout
> hlsl_d3d9: Timeout
> reflection: Timeout
> d3drm:
> d3drm: Timeout
> vector: Timeout
> d3dx10_34:
> d3dx10: Timeout
> d3dx10_35:
> d3dx10: Timeout
> d3dx10_36:
> d3dx10: Timeout
> d3dx10_37:
> d3dx10: Timeout
> d3dx10_38:
> d3dx10: Timeout
> d3dx10_39:
> d3dx10: Timeout
> d3dx10_40:
> d3dx10: Timeout
> d3dx10_41:
> d3dx10: Timeout
> d3dx10_42:
> d3dx10: Timeout
> d3dx10_43:
> d3dx10: Timeout
> d3dx11_42:
> d3dx11: Timeout
> d3dx11_43:
> d3dx11: Timeout
> d3dx9_36:
> asm: Timeout
> core: Timeout
> effect: Timeout
> line: Timeout
> Report validation errors:
> math: Timeout
> === debian11 (build log) ===
> WineRunWineTest.pl:error: The task timed out

Well I changed the tests a bit, but it still didn't solve it, although
it's less hacky. So I'll just skip this test in this particular case here.

Also I check for NULL window to prevent crash since it can be detached.
(unlikely to happen in practice but…)