Mir

Comment 9 for bug 1394369

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

See comment #3. Although that sounds like a kludge it would be important for us to know if some CPU regression has triggered this.

We've gone almost a year without it being a real problem, so I'd be more concerned about some CPU usage regression that might be causing this than the test itself...