This test consumes a huge amount of CPU. On Windows, it additionally starves other tests from getting scheduled - for long enough that those tests time out and fail. Historically tests starting shortly after this test are the most likely to fail. Once we've seen all CPU's, we will no longer do anything useful - so check for that, and finish up early whenever possible.pull/4626/head
parent
383ffacb00
commit
d3917ab790
1 changed files with 7 additions and 1 deletions
Loading…
Reference in new issue