[PATCH 2/5] quartz/vmr9: Don't expose IVMRMonitorConfig9 from the VMR7.

[Marvin]

Hi,

While running your changed tests, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?

Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=80989

Your paranoid android.


=== w1064v1809 (32 bit report) ===

quartz:
vmr7.c:2117: Test failed: Got unexpected status 0.
vmr7.c:2120: Test failed: Wait timed out.
vmr7.c:2128: Test failed: Got unexpected status 0x400040.

=== w10pro64 (32 bit report) ===

quartz:
vmr7.c:2117: Test failed: Got unexpected status 0.
vmr7.c:2120: Test failed: Wait timed out.
vmr7.c:2128: Test failed: Got unexpected status 0x400040.

=== w10pro64_2scr (32 bit report) ===

quartz:
vmr7.c:2117: Test failed: Got unexpected status 0.
vmr7.c:2120: Test failed: Wait timed out.
vmr7.c:2128: Test failed: Got unexpected status 0x400040.

=== w10pro64_2scr (64 bit report) ===

quartz:
vmr7.c:2117: Test failed: Got unexpected status 0.
vmr7.c:2120: Test failed: Wait timed out.
vmr7.c:2128: Test failed: Got unexpected status 0x480048.

=== w10pro64_ar (64 bit report) ===

quartz:
vmr7.c:1216: Test failed: Got hr 0x1.