https://bugs.winehq.org/show_bug.cgi?id=40191
--- Comment #3 from Sebastian Lackner sebastian@fds-team.de --- (In reply to François Gouget from comment #2)
Based on the WineTest results:
- It only fails on real hardware and the TestBot only runs it on QEMU VMs.
- It fails the same way whether the machine is running Windows 8, 8.1 or 10.
- It fails the same way for 32 and 64 bit tests.
- In every failing case the the SpinCount value is 33556432 or 0x020007d0.
Does this value mean anything?
Maybe it's a CPU topology issue: all VMs emulate a dual single-core processor systems while the failures happen on single multi-core processor machines.
The exact value of SpinCount does not matter in this case and the test was written to show a different aspect (mainly the DebugInfo field) - so marking this behavior on Win 8+ as broken should be fine.
Most likely it has to do with the different number of cores, spin-locking is only useful on multiprocessor systems. Nevertheless, is there any chance that we could also get a testbot VM with more than one core, to find such issues a bit earlier in the future? It could also be interesting for other synchronization related functions which might behave different on multiprocessor systems.