Re: [encrypted-media-tests] Extend timeout on all DRM tests that were not already long timeouts. (#4142)

Having look at this I think the problem is this: the check stability run checks 10 iterations of the changed test files. It does not check for passes or fails, rather it checks to see if the output is consistent. In the case of the EME tests this appears to be a timeout of each test. So for small changes it's no problem, but if you change a lot of tests the iterations take longer. There's a global timeout, where if the 10 iterations take longer than, the suite fails. As a result of a large number of files being changed, combined with their increased timeouts we're running into the global limit. 

I'm mindful that if a large number of encrypted-media tests are changed in future this issue will repeat. Thoughts?

View on GitHub: https://github.com/w3c/web-platform-tests/pull/4142#issuecomment-268406247

Received on Wednesday, 21 December 2016 01:10:38 UTC